CVE-2024-13401: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in naa986 Payment Button for PayPal
CVE-2024-13401 is a stored cross-site scripting (XSS) vulnerability in the Payment Button for PayPal WordPress plugin (versions up to 1. 2. 3. 35). It arises from improper input sanitization and output escaping in the 'wp_paypal_checkout' shortcode, allowing authenticated users with contributor-level access or higher to inject malicious scripts. These scripts execute whenever any user views the compromised page, potentially leading to session hijacking, defacement, or other malicious actions. The vulnerability has a CVSS score of 6. 4 (medium severity) and does not require user interaction for exploitation. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or applying mitigations to prevent exploitation.
AI Analysis
Technical Summary
CVE-2024-13401 is a stored cross-site scripting vulnerability affecting the Payment Button for PayPal plugin for WordPress, specifically in all versions up to and including 1.2.3.35. The vulnerability stems from insufficient sanitization and escaping of user-supplied attributes within the plugin's 'wp_paypal_checkout' shortcode. Authenticated attackers with contributor-level privileges or higher can exploit this flaw by injecting arbitrary JavaScript code into pages or posts that utilize this shortcode. Because the malicious script is stored persistently in the WordPress database, it executes every time a user accesses the infected page, potentially compromising user sessions, stealing cookies, or performing unauthorized actions on behalf of users. The vulnerability does not require user interaction beyond visiting the affected page and has a CVSS 3.1 base score of 6.4, reflecting its medium severity. The attack vector is network-based with low attack complexity, requiring privileges but no user interaction, and impacts confidentiality and integrity with no effect on availability. No official patches or fixes have been linked yet, and no known exploits have been observed in the wild. The vulnerability is classified under CWE-79, which covers improper neutralization of input during web page generation leading to cross-site scripting.
Potential Impact
The primary impact of this vulnerability is the potential for attackers with contributor-level access to inject malicious scripts that execute in the context of other users visiting the compromised pages. This can lead to theft of authentication cookies, session hijacking, defacement, unauthorized actions performed with victim user privileges, and potential pivoting to further attacks within the WordPress environment. Organizations running websites with this plugin are at risk of reputational damage, data leakage, and unauthorized access. Since contributor-level access is required, the threat is somewhat limited to insiders or compromised accounts with elevated privileges, but the scope includes any user who views the infected content, including administrators. The vulnerability affects confidentiality and integrity but does not impact availability. Given the widespread use of WordPress and PayPal payment buttons, many small to medium businesses and e-commerce sites could be affected globally.
Mitigation Recommendations
1. Immediately restrict contributor-level and higher access to trusted users only, and audit existing user privileges to reduce risk exposure. 2. Monitor and review all content that uses the 'wp_paypal_checkout' shortcode for suspicious or unauthorized script injections. 3. Apply strict input validation and output escaping manually if patching is not yet available, for example by sanitizing shortcode attributes before rendering. 4. Disable or remove the Payment Button for PayPal plugin until an official patch or update is released. 5. Employ Web Application Firewalls (WAFs) with rules to detect and block common XSS payloads targeting this plugin. 6. Educate content contributors about the risks of injecting untrusted content and enforce secure content creation policies. 7. Regularly update WordPress core, plugins, and themes to the latest versions once patches are available. 8. Implement Content Security Policy (CSP) headers to reduce the impact of injected scripts executing in browsers.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, India, Brazil, Japan, Netherlands
CVE-2024-13401: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in naa986 Payment Button for PayPal
Description
CVE-2024-13401 is a stored cross-site scripting (XSS) vulnerability in the Payment Button for PayPal WordPress plugin (versions up to 1. 2. 3. 35). It arises from improper input sanitization and output escaping in the 'wp_paypal_checkout' shortcode, allowing authenticated users with contributor-level access or higher to inject malicious scripts. These scripts execute whenever any user views the compromised page, potentially leading to session hijacking, defacement, or other malicious actions. The vulnerability has a CVSS score of 6. 4 (medium severity) and does not require user interaction for exploitation. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or applying mitigations to prevent exploitation.
AI-Powered Analysis
Technical Analysis
CVE-2024-13401 is a stored cross-site scripting vulnerability affecting the Payment Button for PayPal plugin for WordPress, specifically in all versions up to and including 1.2.3.35. The vulnerability stems from insufficient sanitization and escaping of user-supplied attributes within the plugin's 'wp_paypal_checkout' shortcode. Authenticated attackers with contributor-level privileges or higher can exploit this flaw by injecting arbitrary JavaScript code into pages or posts that utilize this shortcode. Because the malicious script is stored persistently in the WordPress database, it executes every time a user accesses the infected page, potentially compromising user sessions, stealing cookies, or performing unauthorized actions on behalf of users. The vulnerability does not require user interaction beyond visiting the affected page and has a CVSS 3.1 base score of 6.4, reflecting its medium severity. The attack vector is network-based with low attack complexity, requiring privileges but no user interaction, and impacts confidentiality and integrity with no effect on availability. No official patches or fixes have been linked yet, and no known exploits have been observed in the wild. The vulnerability is classified under CWE-79, which covers improper neutralization of input during web page generation leading to cross-site scripting.
Potential Impact
The primary impact of this vulnerability is the potential for attackers with contributor-level access to inject malicious scripts that execute in the context of other users visiting the compromised pages. This can lead to theft of authentication cookies, session hijacking, defacement, unauthorized actions performed with victim user privileges, and potential pivoting to further attacks within the WordPress environment. Organizations running websites with this plugin are at risk of reputational damage, data leakage, and unauthorized access. Since contributor-level access is required, the threat is somewhat limited to insiders or compromised accounts with elevated privileges, but the scope includes any user who views the infected content, including administrators. The vulnerability affects confidentiality and integrity but does not impact availability. Given the widespread use of WordPress and PayPal payment buttons, many small to medium businesses and e-commerce sites could be affected globally.
Mitigation Recommendations
1. Immediately restrict contributor-level and higher access to trusted users only, and audit existing user privileges to reduce risk exposure. 2. Monitor and review all content that uses the 'wp_paypal_checkout' shortcode for suspicious or unauthorized script injections. 3. Apply strict input validation and output escaping manually if patching is not yet available, for example by sanitizing shortcode attributes before rendering. 4. Disable or remove the Payment Button for PayPal plugin until an official patch or update is released. 5. Employ Web Application Firewalls (WAFs) with rules to detect and block common XSS payloads targeting this plugin. 6. Educate content contributors about the risks of injecting untrusted content and enforce secure content creation policies. 7. Regularly update WordPress core, plugins, and themes to the latest versions once patches are available. 8. Implement Content Security Policy (CSP) headers to reduce the impact of injected scripts executing in browsers.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-01-14T18:19:32.093Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6e54b7ef31ef0b59e5a9
Added to database: 2/25/2026, 9:49:08 PM
Last enriched: 2/26/2026, 1:28:43 AM
Last updated: 2/26/2026, 9:59:16 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-28138: Deserialization of Untrusted Data in Stylemix uListing
HighCVE-2026-28136: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in VeronaLabs WP SMS
HighCVE-2026-28132: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in villatheme WooCommerce Photo Reviews
HighCVE-2026-28131: Insertion of Sensitive Information Into Sent Data in WPVibes Elementor Addon Elements
HighCVE-2026-28083: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in UX-themes Flatsome
HighActions
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.