CVE-2025-10375

Web Accessibility By accessiBe <= 2.10 - Cross-Site Request Forgery

2025-10-10 00:00
Moose Love

Strategic Overview

Status
Patched in 2.11
Affected Plugin
Web Accessibility by accessiBe
Affected Version
<= 2.10
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-10375
View all Web Accessibility by accessiBe vulnerabilities

At a glance

CVE-2025-10375 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Web Accessibility by accessiBe WordPress plugin, affecting versions <= 2.10. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.11; sites on affected versions should update now. Disclosed October 2025, reported by Moose Love.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Web Accessibility by accessiBe <= 2.10 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Web Accessibility by accessiBe the fix is 2.11: builds <= 2.10 are affected, anything from 2.11 onward is not.

Remediation

Update to version 2.11, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Web Accessibility by accessiBe: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Web Accessibility by accessiBe 2.11 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-10375https://www.wordfence.com/threat-intel/vulnerabilities/id/e3aac40c-1576-45b5-90f8-14ff05c089c7https://nvd.nist.gov/vuln/detail/CVE-2025-10375

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C