CVE-2026-2502
Stored XSS in WordPress xmlrpc Attacks Blocker Plugin Logs
Publication date: 2026-02-19
Last updated on: 2026-02-19
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | xmlrpc_attacks_blocker | to 1.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The xmlrpc attacks blocker plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in versions up to and including 1.0. This vulnerability arises because the plugin trusts and logs the 'X-Forwarded-For' HTTP header, which can be controlled by an attacker. The plugin then renders these logged entries on the debug log page without properly escaping the output, allowing an attacker to inject malicious web scripts.
These injected scripts execute when an administrator views the debug log page, potentially compromising the administrator's session or the security of the WordPress site.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to inject malicious scripts that execute in the context of an administrator's browser when they view the debug log page. This can lead to unauthorized actions such as session hijacking, defacement, or further compromise of the WordPress site.
Since the attack requires the administrator to view the debug log page, the impact depends on the administrator's interaction, but it can still result in significant security risks including loss of integrity and confidentiality.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know