Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11763: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in rustybadrobot Display Pages Shortcode

0
Medium
VulnerabilityCVE-2025-11763cvecve-2025-11763cwe-79
Published: Fri Nov 21 2025 (11/21/2025, 07:31:57 UTC)
Source: CVE Database V5
Vendor/Project: rustybadrobot
Product: Display Pages Shortcode

Description

The Display Pages Shortcode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'column_count' parameter in the [display-pages] shortcode in all versions up to, and including, 1.1. This is due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AI-Powered Analysis

AILast updated: 11/28/2025, 08:43:52 UTC

Technical Analysis

CVE-2025-11763 is a stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79, found in the Display Pages Shortcode plugin for WordPress developed by rustybadrobot. This vulnerability exists in all versions up to and including 1.1. The root cause is insufficient sanitization and escaping of the 'column_count' parameter within the [display-pages] shortcode, which allows an authenticated attacker with contributor-level or higher privileges to inject arbitrary JavaScript code into WordPress pages. When any user accesses a page containing the injected shortcode, the malicious script executes in their browser context, potentially leading to session hijacking, unauthorized actions on behalf of users, or the theft of sensitive information. The vulnerability requires authentication but no user interaction beyond viewing the compromised page. The CVSS 3.1 base score is 6.4, indicating a medium severity with network attack vector, low attack complexity, and privileges required at the contributor level. The scope is changed, meaning the vulnerability can affect resources beyond the initially compromised component. No patches or official fixes have been released at the time of publication, and no active exploitation has been reported. This vulnerability highlights the importance of proper input validation and output encoding in WordPress plugins, especially those that accept user-controllable parameters in shortcodes.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to websites and intranet portals running WordPress with the Display Pages Shortcode plugin installed. Attackers with contributor-level access—often achievable through compromised accounts or insider threats—can inject persistent malicious scripts that execute in the context of any user visiting the affected pages. This can lead to session hijacking, unauthorized actions such as content manipulation or privilege escalation, and potential data leakage. Organizations relying on WordPress for public-facing or internal content management may face reputational damage, regulatory scrutiny under GDPR if personal data is compromised, and operational disruptions. The vulnerability does not directly impact availability but threatens confidentiality and integrity of user sessions and data. Since the attack vector is network-based and requires authentication, the risk is somewhat mitigated by strong access controls but remains significant in environments with multiple contributors or weak account management practices.

Mitigation Recommendations

European organizations should immediately audit their WordPress installations to identify if the Display Pages Shortcode plugin is in use and confirm the version. Until an official patch is released, mitigation should include: 1) Restrict contributor-level access strictly to trusted users and review existing user privileges to minimize the attack surface. 2) Implement Web Application Firewall (WAF) rules to detect and block suspicious payloads targeting the 'column_count' parameter in shortcode requests. 3) Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. 4) Monitor logs for unusual shortcode parameter usage or unexpected page content changes. 5) Educate content contributors about the risks of injecting untrusted input into shortcodes. 6) Consider temporarily disabling or removing the plugin if it is not essential. 7) Stay alert for official patches or updates from the vendor and apply them promptly. 8) Conduct regular security assessments and penetration testing focused on WordPress plugins and user privilege management.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-14T21:11:20.360Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69202359cf2d47c38997b3c3

Added to database: 11/21/2025, 8:31:21 AM

Last enriched: 11/28/2025, 8:43:52 AM

Last updated: 1/7/2026, 6:09:53 AM

Views: 47

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats