CVE-2025-23837: WordPress One Backend Language Plugin <= 1.0 - Reflected Cross Site Scripting (XSS) vulnerability
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in martinjuhasz One Backend Language one-backend-language allows Reflected XSS.This issue affects One Backend Language: from n/a through <= 1.0.
Security readout for executives and security teams
Plain-English summary
CVE-2025-23837 is a reflected cross-site scripting issue in the WordPress One Backend Language plugin through version 1.0. An attacker would need to lure a user into interacting with malicious content, but successful exploitation could affect the user’s browser session and site trust.
Executive priority
Treat this as a high-priority WordPress hygiene issue where the plugin is present. It is not listed as actively exploited in the provided sources, but XSS in WordPress can support account abuse, reputational harm, and follow-on compromise if privileged users are targeted.
Technical view
The issue is CWE-79 improper input neutralization during web page generation in martinjuhasz One Backend Language. The CVSS 3.1 score is 7.1, with network attack vector, low complexity, no privileges required, and required user interaction. Scope is changed with low confidentiality, integrity, and availability impacts.
Likely exposure
Exposure appears limited to WordPress sites with the one-backend-language plugin installed at version 1.0 or earlier. The bundle’s affected-version metadata is sparse, so teams should verify the installed plugin slug and version directly in their WordPress inventory.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The attack model is reflected XSS, which generally depends on a targeted user interacting with attacker-controlled content. No exploit maturity or public weaponization evidence is provided in the bundle.
Researcher notes
The CVE record identifies reflected XSS in One Backend Language through version 1.0 and assigns CVSS 7.1. The provided data does not include a patch version, exploit proof, or detailed vulnerable parameter, so validation should remain non-destructive and inventory-focused.
Mitigation direction
Check Patchstack and vendor guidance for a fixed version or official mitigation.
Upgrade the plugin if a safe vendor-confirmed release is available.
Disable or remove the plugin if it is not required for business operations.
Restrict administrative access and monitor suspicious WordPress user activity.
Validation and detection
Inventory WordPress sites for the one-backend-language plugin slug.
Confirm whether installed versions are 1.0 or earlier.
Review web logs for suspicious requests involving the affected plugin.
Verify remediation against vendor or Patchstack guidance after changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.