CVE-2026-2502
Awaiting Analysis Awaiting Analysis - Queue
Stored XSS in WordPress xmlrpc Attacks Blocker Plugin Logs

Publication date: 2026-02-19

Last updated on: 2026-02-19

Assigner: Wordfence

Description
The xmlrpc attacks blocker plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.0, via the 'X-Forwarded-For' HTTP header. This is due to the plugin trusting and logging attacker-controlled IP header data and rendering debug log entries without output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the debug log page.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-19
Last Modified
2026-02-19
Generated
2026-06-16
AI Q&A
2026-02-19
EPSS Evaluated
2026-06-14
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wordfence xmlrpc_attacks_blocker to 1.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-2502. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart