CVE-2025-13966 json
Paypal Payment Shortcode <= 1.01 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'buttom_image' Shortcode Attribute
published 2025-12-12 10 mo ago modified 2026-10-07 32 d ago also EUVD-2025-202977
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
The Paypal Payment Shortcode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'buttom_image' parameter of the [paypal-shortcode] shortcode in all versions up to, and including, 1.01 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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10 mo ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- sonlamtn200 Paypal Payment Shortcode
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/b0b1fbb1-fc2c-4eb9-89c6-364ca8c385db?source=cve
- plugins.trac.wordpress.org /browser/paypal-payments-shortcode/trunk/sls-paypal-payments-shortcode.php#L10
- plugins.trac.wordpress.org /browser/paypal-payments-shortcode/tags/1.01/sls-paypal-payments-shortcode.php#L10
- plugins.trac.wordpress.org /browser/paypal-payments-shortcode/trunk/sls-paypal-payments-shortcode.php#L55
- plugins.trac.wordpress.org /browser/paypal-payments-shortcode/tags/1.01/sls-paypal-payments-shortcode.php#L55
Sources
- CVE List CVE-2025-13966
- NVD CVE-2025-13966
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.