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-12667: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in paul1999 GitHub Gist Shortcode Plugin

0
Medium
VulnerabilityCVE-2025-12667cvecve-2025-12667cwe-79
Published: Tue Nov 11 2025 (11/11/2025, 03:30:53 UTC)
Source: CVE Database V5
Vendor/Project: paul1999
Product: GitHub Gist Shortcode Plugin

Description

The GitHub Gist Shortcode Plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' parameter of the 'gist' shortcode in all versions up to, and including, 0.2 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/18/2025, 04:23:22 UTC

Technical Analysis

CVE-2025-12667 is a stored Cross-Site Scripting (XSS) vulnerability identified in the paul1999 GitHub Gist Shortcode Plugin for WordPress, affecting all versions up to and including 0.2. The vulnerability stems from improper neutralization of input during web page generation, specifically inadequate sanitization and escaping of the 'id' parameter within the 'gist' shortcode. Authenticated users with Contributor-level permissions or higher can exploit this flaw by injecting arbitrary JavaScript code into WordPress pages or posts that utilize this shortcode. When other users access these pages, the malicious scripts execute in their browsers, potentially compromising session tokens, redirecting users, or performing unauthorized actions on their behalf. The vulnerability does not require user interaction beyond visiting the infected page, and it can affect the confidentiality and integrity of user sessions and data. The CVSS 3.1 score of 6.4 reflects a medium severity, with an attack vector over the network, low attack complexity, and privileges required at the contributor level. No public exploits have been reported yet, but the vulnerability is significant due to the widespread use of WordPress and the plugin's functionality that facilitates embedding external content. The plugin's lack of proper input validation and output escaping is the root cause, highlighting the need for secure coding practices in plugin development.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to websites and intranet portals running WordPress with the vulnerable GitHub Gist Shortcode Plugin installed. Exploitation can lead to session hijacking, unauthorized actions performed under the victim's credentials, defacement, or distribution of malware via injected scripts. This can damage organizational reputation, lead to data breaches, and disrupt business operations. Since the attack requires authenticated contributor-level access, insider threats or compromised contributor accounts are the most likely vectors. The scope includes any user accessing the infected pages, potentially affecting employees, partners, or customers. Given the popularity of WordPress in Europe for corporate and public sector websites, the impact can be widespread, especially for organizations that allow multiple contributors to publish content. The vulnerability's ability to compromise integrity and confidentiality without requiring user interaction increases its risk profile. Although availability is not directly impacted, the indirect effects of exploitation could lead to service disruptions or increased support costs.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Immediately review and restrict Contributor-level permissions to trusted users only, minimizing the risk of malicious shortcode injection. 2) Disable or remove the paul1999 GitHub Gist Shortcode Plugin if it is not essential, or upgrade to a patched version once available. 3) Implement web application firewalls (WAFs) with rules to detect and block suspicious shortcode usage or script injection patterns. 4) Conduct regular audits of WordPress content for unauthorized or suspicious shortcode entries. 5) Employ Content Security Policy (CSP) headers to restrict the execution of inline scripts and reduce XSS impact. 6) Educate content contributors about secure content publishing practices and the risks of injecting untrusted code. 7) Monitor logs for unusual contributor activity or unexpected changes in pages containing the 'gist' shortcode. 8) Use security plugins that provide input sanitization and output escaping enhancements. These targeted measures go beyond generic advice by focusing on contributor access control, plugin management, and proactive detection tailored to this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-03T21:30:51.091Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6912b13314bc3e00ba783db6

Added to database: 11/11/2025, 3:44:51 AM

Last enriched: 11/18/2025, 4:23:22 AM

Last updated: 11/20/2025, 9:52:55 AM

Views: 12

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats