CVE-2025-10375 MEDIUM

CVE-2025-10375: Web Accessibility By accessiBe <= 2.10 - Cross-Site Request Forgery

Vendor Accessibewp
Product Web Accessibility by accessiBe
Weakness CWE-352 · CSRF
Published October 11, 2025
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

The Web Accessibility By accessiBe plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.10. This is due to missing nonce validation on multiple AJAX actions including accessibe_signup, accessibe_login, accessibe_license_trial, accessibe_modify_config, and accessibe_add_verification_page. This makes it possible for unauthenticated attackers to modify plugin settings and create verification files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Explanation of Vulnerability in Simple Terms

02Summary

Web Accessibility by accessiBe versions 2.10 and earlier are vulnerable to cross-site request forgery (CSRF) attacks. An attacker can craft a malicious webpage that, when visited by a site administrator, performs unwanted actions on the site without their knowledge. The vulnerability requires the admin to visit the attacker's page while logged into their WordPress site. No sensitive data is exposed, but site settings or content could be modified.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on a site (change settings, modify content) by tricking an admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

Administrators could unknowingly authorize changes to site configuration or content if they visit a malicious link while logged in.

Conditions required to exploit

05Prerequisites

Site admin must visit attacker-controlled webpage while logged into WordPress. No special privileges or authentication bypass needed.

Key dates

06Disclosure timeline

October 11, 2025 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE