CVE-2025-23834: Links/Problem Reporter XSS Vulnerability

CVE-2025-23834 Overview

CVE-2025-23834 is a reflected Cross-Site Scripting (XSS) vulnerability in the RaminMT Links/Problem Reporter (report-broken-links) WordPress plugin. The flaw affects all plugin versions up to and including 2.6.0. The plugin fails to properly neutralize user-supplied input during web page generation, allowing attackers to inject malicious scripts that execute in the victim's browser. The vulnerability is tracked under [CWE-79] (Improper Neutralization of Input During Web Page Generation).

Critical Impact

An unauthenticated attacker can craft a malicious URL that, when clicked by a victim, executes arbitrary JavaScript in the victim's browser session, potentially leading to session theft, credential harvesting, or administrative account compromise.

Affected Products

• RaminMT Links/Problem Reporter (report-broken-links) WordPress plugin
• All versions from n/a through <= 2.6.0
• WordPress sites with the vulnerable plugin installed and active

Discovery Timeline

• 2025-01-23 - CVE-2025-23834 published to the National Vulnerability Database
• 2026-04-23 - Last updated in the NVD database

Technical Details for CVE-2025-23834

Vulnerability Analysis

The Links/Problem Reporter plugin processes user-controlled parameters and reflects them back into the rendered HTML response without proper output encoding or input sanitization. When a victim visits a crafted URL containing JavaScript payloads in vulnerable parameters, the browser executes the injected code within the context of the WordPress site's origin.

Reflected XSS attacks require user interaction, typically delivered through phishing emails, malicious links, or social engineering. The scope change in the impact metric indicates the injected script can affect resources beyond the vulnerable component, including authenticated administrator sessions. EPSS data places the probability of exploitation at 0.187% with a percentile rank near 40, reflecting moderate predicted exploitation activity.

Root Cause

The root cause is the absence of contextual output encoding when rendering request parameters into the HTML response. The plugin trusts input received through HTTP request parameters and writes it directly into the page markup. Standard WordPress functions such as esc_html(), esc_attr(), or esc_url() are not consistently applied to these data flows.

Attack Vector

The attack vector is network-based and requires user interaction. An attacker crafts a URL pointing to the vulnerable plugin endpoint, embedding a JavaScript payload within a reflected parameter. The attacker then delivers this URL to a target through phishing, forum posts, comments, or other social channels. When the victim opens the link in an authenticated session, the script runs with the privileges of that session.

No verified proof-of-concept code is available in public sources. Refer to the Patchstack Vulnerability Report for additional technical context.

Detection Methods for CVE-2025-23834

Indicators of Compromise

• HTTP request logs containing URL-encoded <script>, onerror=, onload=, or javascript: patterns targeting plugin endpoints
• Unexpected outbound requests from administrator browsers to attacker-controlled domains shortly after clicking inbound links
• Anomalous WordPress administrator session creation or privilege changes following suspicious link clicks
• Web server access logs showing reflected parameters containing HTML entities or encoded script payloads

Detection Strategies

• Deploy Web Application Firewall (WAF) rules that inspect query strings and POST bodies for XSS signatures targeting the report-broken-links plugin paths
• Enable WordPress audit logging to capture parameter contents on requests to plugin endpoints
• Hunt for suspicious referrer headers and URL parameters in HTTP access logs using regex matches on common XSS payload patterns

Monitoring Recommendations

• Monitor authenticated administrator sessions for unusual JavaScript-driven actions such as user creation, plugin installation, or option changes
• Track outbound DNS and HTTP traffic from administrator workstations to identify data exfiltration following XSS exploitation
• Alert on WordPress plugin version inventories that still report report-broken-links versions <= 2.6.0

How to Mitigate CVE-2025-23834

Immediate Actions Required

• Identify all WordPress installations running the Links/Problem Reporter plugin and confirm installed versions
• Deactivate and remove the plugin from any site running version 2.6.0 or earlier until a patched version is verified
• Force password resets and invalidate active sessions for administrator accounts if exploitation is suspected
• Apply WAF rules blocking XSS payload patterns against plugin endpoints as a compensating control

Patch Information

No fixed version is identified in the available advisory data. Administrators should consult the Patchstack Vulnerability Report and the plugin's WordPress.org page for updated release information. If no patch is available, removing the plugin is the recommended action.

Workarounds

• Restrict access to WordPress admin interfaces using IP allowlists or VPN-only access to limit attack surface
• Deploy a Content Security Policy (CSP) header that disallows inline scripts and unsanctioned script sources
• Educate administrative users on phishing risks and the danger of clicking unfamiliar links while authenticated to WordPress
• Replace the vulnerable plugin with an alternative broken-link reporting solution that receives active security maintenance