CVE-2024-11873: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in glomex glomex oEmbed
CVE-2024-11873 is a stored cross-site scripting (XSS) vulnerability in the glomex oEmbed WordPress plugin affecting all versions up to 0. 9. 1. It arises from improper input sanitization and output escaping in the 'glomex_integration' shortcode, allowing authenticated users with contributor-level or higher privileges to inject malicious scripts. These scripts execute whenever any user accesses the compromised page, potentially leading to session hijacking, defacement, or unauthorized actions. The vulnerability has a CVSS score of 6. 4, indicating medium severity, and does not require user interaction but does require some level of authenticated access. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or mitigating this issue to prevent exploitation.
AI Analysis
Technical Summary
CVE-2024-11873 is a stored cross-site scripting vulnerability identified in the glomex oEmbed plugin for WordPress, which is widely used to embed video content. The flaw exists in all versions up to and including 0.9.1 due to insufficient sanitization and escaping of user-supplied attributes within the 'glomex_integration' shortcode. This improper neutralization of input (CWE-79) allows authenticated attackers with contributor-level or higher privileges to inject arbitrary JavaScript code into pages or posts. Because the malicious script is stored persistently, it executes in the context of any user who views the infected page, potentially compromising user sessions, stealing cookies, or performing actions on behalf of users without their consent. The vulnerability requires no user interaction but does require authenticated access, which limits exploitation to users with some level of trust within the WordPress environment. The CVSS 3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, and privileges required. No patches or official fixes were linked at the time of publication, and no known exploits have been reported in the wild. This vulnerability highlights the importance of proper input validation and output encoding in WordPress plugins, especially those that accept user input for dynamic content generation.
Potential Impact
The impact of CVE-2024-11873 can be significant for organizations running WordPress sites with the glomex oEmbed plugin installed. Successful exploitation allows attackers with contributor-level access to inject persistent malicious scripts that execute in the browsers of site visitors and administrators. This can lead to session hijacking, theft of sensitive information such as authentication cookies, unauthorized actions performed on behalf of users, defacement of website content, and potential spread of malware. Since the vulnerability requires authenticated access, the risk is higher in environments where contributor or higher roles are assigned to untrusted or compromised users. For high-traffic websites or those handling sensitive data, the consequences can include reputational damage, data breaches, and loss of user trust. Additionally, the scope of affected systems is broad as all versions of the plugin up to 0.9.1 are vulnerable, and WordPress remains a dominant CMS worldwide, increasing the potential attack surface.
Mitigation Recommendations
To mitigate CVE-2024-11873, organizations should immediately update the glomex oEmbed plugin to a version that addresses this vulnerability once available. In the absence of an official patch, administrators should consider disabling or removing the plugin to eliminate the attack vector. Restrict contributor-level and higher privileges to trusted users only and review user roles to minimize the risk of insider threats. Implement Web Application Firewall (WAF) rules to detect and block suspicious script injection attempts targeting the 'glomex_integration' shortcode. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on affected pages. Regularly audit WordPress plugins for security updates and conduct penetration testing focusing on user input handling. Educate site administrators and contributors about the risks of XSS and the importance of secure content management practices.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, India, Brazil, Japan
CVE-2024-11873: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in glomex glomex oEmbed
Description
CVE-2024-11873 is a stored cross-site scripting (XSS) vulnerability in the glomex oEmbed WordPress plugin affecting all versions up to 0. 9. 1. It arises from improper input sanitization and output escaping in the 'glomex_integration' shortcode, allowing authenticated users with contributor-level or higher privileges to inject malicious scripts. These scripts execute whenever any user accesses the compromised page, potentially leading to session hijacking, defacement, or unauthorized actions. The vulnerability has a CVSS score of 6. 4, indicating medium severity, and does not require user interaction but does require some level of authenticated access. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or mitigating this issue to prevent exploitation.
AI-Powered Analysis
Technical Analysis
CVE-2024-11873 is a stored cross-site scripting vulnerability identified in the glomex oEmbed plugin for WordPress, which is widely used to embed video content. The flaw exists in all versions up to and including 0.9.1 due to insufficient sanitization and escaping of user-supplied attributes within the 'glomex_integration' shortcode. This improper neutralization of input (CWE-79) allows authenticated attackers with contributor-level or higher privileges to inject arbitrary JavaScript code into pages or posts. Because the malicious script is stored persistently, it executes in the context of any user who views the infected page, potentially compromising user sessions, stealing cookies, or performing actions on behalf of users without their consent. The vulnerability requires no user interaction but does require authenticated access, which limits exploitation to users with some level of trust within the WordPress environment. The CVSS 3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, and privileges required. No patches or official fixes were linked at the time of publication, and no known exploits have been reported in the wild. This vulnerability highlights the importance of proper input validation and output encoding in WordPress plugins, especially those that accept user input for dynamic content generation.
Potential Impact
The impact of CVE-2024-11873 can be significant for organizations running WordPress sites with the glomex oEmbed plugin installed. Successful exploitation allows attackers with contributor-level access to inject persistent malicious scripts that execute in the browsers of site visitors and administrators. This can lead to session hijacking, theft of sensitive information such as authentication cookies, unauthorized actions performed on behalf of users, defacement of website content, and potential spread of malware. Since the vulnerability requires authenticated access, the risk is higher in environments where contributor or higher roles are assigned to untrusted or compromised users. For high-traffic websites or those handling sensitive data, the consequences can include reputational damage, data breaches, and loss of user trust. Additionally, the scope of affected systems is broad as all versions of the plugin up to 0.9.1 are vulnerable, and WordPress remains a dominant CMS worldwide, increasing the potential attack surface.
Mitigation Recommendations
To mitigate CVE-2024-11873, organizations should immediately update the glomex oEmbed plugin to a version that addresses this vulnerability once available. In the absence of an official patch, administrators should consider disabling or removing the plugin to eliminate the attack vector. Restrict contributor-level and higher privileges to trusted users only and review user roles to minimize the risk of insider threats. Implement Web Application Firewall (WAF) rules to detect and block suspicious script injection attempts targeting the 'glomex_integration' shortcode. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on affected pages. Regularly audit WordPress plugins for security updates and conduct penetration testing focusing on user input handling. Educate site administrators and contributors about the risks of XSS and the importance of secure content management practices.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2024-11-27T15:23:47.846Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6e24b7ef31ef0b596a55
Added to database: 2/25/2026, 9:48:20 PM
Last enriched: 2/26/2026, 7:59:45 AM
Last updated: 2/26/2026, 8:55:17 AM
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-1698: CWE-644 Improper Neutralization of HTTP Headers for Scripting Syntax in arcinfo PcVue
MediumCVE-2026-1697: CWE-614 Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in arcinfo PcVue
MediumCVE-2026-1696: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in arcinfo PcVue
LowCVE-2026-1695: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in arcinfo PcVue
MediumCVE-2026-1694: CWE-201 Insertion of Sensitive Information into Sent Data in arcinfo PcVue
LowActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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.