CVE-2024-13519: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in webwizardsdev MarketKing — Ultimate WooCommerce Multivendor Marketplace Solution
CVE-2024-13519 is a stored Cross-Site Scripting (XSS) vulnerability in the MarketKing — Ultimate WooCommerce Multivendor Marketplace Solution WordPress plugin. It affects all versions up to 1. 9. 80 and allows authenticated users with Shop Manager-level permissions or higher to inject malicious scripts via plugin settings. The vulnerability arises from insufficient input sanitization and output escaping, specifically impacting multi-site WordPress installations or those with unfiltered_html disabled. Exploited scripts execute whenever any user accesses the compromised page, potentially leading to session hijacking or unauthorized actions. The CVSS score is 4. 4 (medium severity), reflecting the need for authentication and high attack complexity. No known exploits are currently reported in the wild. Organizations using this plugin in multi-site environments should prioritize patching or applying mitigations to prevent exploitation.
AI Analysis
Technical Summary
CVE-2024-13519 is a stored Cross-Site Scripting (XSS) vulnerability identified in the MarketKing — Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress, affecting all versions up to and including 1.9.80. The vulnerability stems from improper neutralization of input during web page generation (CWE-79), where the plugin fails to adequately sanitize and escape user-supplied data in its settings interface. This flaw allows authenticated attackers with Shop Manager-level permissions or higher to inject arbitrary JavaScript code into pages rendered by the plugin. The malicious scripts are stored persistently and execute in the context of any user who views the infected page, potentially compromising user sessions, stealing credentials, or performing unauthorized actions on behalf of users. The vulnerability specifically impacts multi-site WordPress installations or single-site setups where the unfiltered_html capability is disabled, limiting the scope but still posing a significant risk in those environments. The CVSS 3.1 base score of 4.4 reflects a medium severity, with network attack vector, high attack complexity, required privileges, no user interaction, and partial confidentiality and integrity impact. No public exploits have been reported to date, but the presence of this vulnerability in a widely used WooCommerce multivendor plugin highlights the importance of timely remediation. The plugin vendor has not yet published a patch, so users must rely on alternative mitigations until an official fix is available.
Potential Impact
The primary impact of CVE-2024-13519 is the potential for attackers with Shop Manager-level access to execute arbitrary JavaScript in the context of other users visiting the affected pages. This can lead to session hijacking, theft of sensitive information such as cookies or credentials, unauthorized actions performed on behalf of users, and potential defacement or redirection attacks. Since the vulnerability is stored XSS, the malicious payload persists and can affect multiple users over time. The requirement for authenticated access with elevated privileges limits the attack surface but does not eliminate risk, especially in environments where Shop Managers are numerous or less trusted. Multi-site WordPress installations and those with unfiltered_html disabled are particularly vulnerable, which may include large e-commerce platforms and marketplaces using WooCommerce. The medium CVSS score reflects moderate risk; however, the potential for lateral movement and privilege escalation through XSS in a multivendor marketplace environment could have significant business and reputational consequences if exploited. Organizations may face data breaches, loss of customer trust, and compliance issues if this vulnerability is left unaddressed.
Mitigation Recommendations
1. Immediate mitigation involves restricting Shop Manager-level permissions to trusted users only, minimizing the number of accounts that can exploit this vulnerability. 2. Monitor and audit plugin settings pages for suspicious or unexpected script injections. 3. Implement Web Application Firewall (WAF) rules to detect and block typical XSS payloads targeting the plugin’s settings interface. 4. Where possible, enable Content Security Policy (CSP) headers to restrict execution of unauthorized scripts on affected pages. 5. Regularly back up WordPress sites and database contents to enable quick restoration if compromise occurs. 6. Until an official patch is released, consider disabling or replacing the MarketKing plugin in multi-site environments or those with unfiltered_html disabled. 7. Educate administrators and Shop Managers about the risks of injecting untrusted content into plugin settings. 8. Follow vendor announcements closely and apply patches promptly once available. 9. Conduct penetration testing focused on XSS vectors in the affected plugin to identify and remediate any additional injection points.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, India, Brazil, France, Netherlands, Japan, Italy, Spain
CVE-2024-13519: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in webwizardsdev MarketKing — Ultimate WooCommerce Multivendor Marketplace Solution
Description
CVE-2024-13519 is a stored Cross-Site Scripting (XSS) vulnerability in the MarketKing — Ultimate WooCommerce Multivendor Marketplace Solution WordPress plugin. It affects all versions up to 1. 9. 80 and allows authenticated users with Shop Manager-level permissions or higher to inject malicious scripts via plugin settings. The vulnerability arises from insufficient input sanitization and output escaping, specifically impacting multi-site WordPress installations or those with unfiltered_html disabled. Exploited scripts execute whenever any user accesses the compromised page, potentially leading to session hijacking or unauthorized actions. The CVSS score is 4. 4 (medium severity), reflecting the need for authentication and high attack complexity. No known exploits are currently reported in the wild. Organizations using this plugin in multi-site environments should prioritize patching or applying mitigations to prevent exploitation.
AI-Powered Analysis
Technical Analysis
CVE-2024-13519 is a stored Cross-Site Scripting (XSS) vulnerability identified in the MarketKing — Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress, affecting all versions up to and including 1.9.80. The vulnerability stems from improper neutralization of input during web page generation (CWE-79), where the plugin fails to adequately sanitize and escape user-supplied data in its settings interface. This flaw allows authenticated attackers with Shop Manager-level permissions or higher to inject arbitrary JavaScript code into pages rendered by the plugin. The malicious scripts are stored persistently and execute in the context of any user who views the infected page, potentially compromising user sessions, stealing credentials, or performing unauthorized actions on behalf of users. The vulnerability specifically impacts multi-site WordPress installations or single-site setups where the unfiltered_html capability is disabled, limiting the scope but still posing a significant risk in those environments. The CVSS 3.1 base score of 4.4 reflects a medium severity, with network attack vector, high attack complexity, required privileges, no user interaction, and partial confidentiality and integrity impact. No public exploits have been reported to date, but the presence of this vulnerability in a widely used WooCommerce multivendor plugin highlights the importance of timely remediation. The plugin vendor has not yet published a patch, so users must rely on alternative mitigations until an official fix is available.
Potential Impact
The primary impact of CVE-2024-13519 is the potential for attackers with Shop Manager-level access to execute arbitrary JavaScript in the context of other users visiting the affected pages. This can lead to session hijacking, theft of sensitive information such as cookies or credentials, unauthorized actions performed on behalf of users, and potential defacement or redirection attacks. Since the vulnerability is stored XSS, the malicious payload persists and can affect multiple users over time. The requirement for authenticated access with elevated privileges limits the attack surface but does not eliminate risk, especially in environments where Shop Managers are numerous or less trusted. Multi-site WordPress installations and those with unfiltered_html disabled are particularly vulnerable, which may include large e-commerce platforms and marketplaces using WooCommerce. The medium CVSS score reflects moderate risk; however, the potential for lateral movement and privilege escalation through XSS in a multivendor marketplace environment could have significant business and reputational consequences if exploited. Organizations may face data breaches, loss of customer trust, and compliance issues if this vulnerability is left unaddressed.
Mitigation Recommendations
1. Immediate mitigation involves restricting Shop Manager-level permissions to trusted users only, minimizing the number of accounts that can exploit this vulnerability. 2. Monitor and audit plugin settings pages for suspicious or unexpected script injections. 3. Implement Web Application Firewall (WAF) rules to detect and block typical XSS payloads targeting the plugin’s settings interface. 4. Where possible, enable Content Security Policy (CSP) headers to restrict execution of unauthorized scripts on affected pages. 5. Regularly back up WordPress sites and database contents to enable quick restoration if compromise occurs. 6. Until an official patch is released, consider disabling or replacing the MarketKing plugin in multi-site environments or those with unfiltered_html disabled. 7. Educate administrators and Shop Managers about the risks of injecting untrusted content into plugin settings. 8. Follow vendor announcements closely and apply patches promptly once available. 9. Conduct penetration testing focused on XSS vectors in the affected plugin to identify and remediate any additional injection points.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-01-17T18:34:32.469Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6e5cb7ef31ef0b59ef30
Added to database: 2/25/2026, 9:49:16 PM
Last enriched: 2/26/2026, 12:16:56 AM
Last updated: 2/26/2026, 8:05:04 AM
Views: 1
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-25191: Uncontrolled Search Path Element in Digital Arts Inc. FinalCode Ver.5 series
HighCVE-2026-23703: Incorrect default permissions in Digital Arts Inc. FinalCode Ver.5 series
HighCVE-2026-1311: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in bearsthemes Worry Proof Backup
HighFinding Signal in the Noise: Lessons Learned Running a Honeypot with AI Assistance [Guest Diary], (Tue, Feb 24th)
MediumCVE-2026-2506: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in motahar1 EM Cost Calculator
MediumActions
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.