CVE-2026-6913 json
Shortcodely <= 1.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'widget_area' Shortcode Attribute
published 2026-05-12 5 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-29411
- 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 10%
- public exploits
- 0
- none known
Summary
The Shortcodely plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'widget_area' parameter in all versions up to, and including, 1.0.1 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
- 5 mo ago
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 10% 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
- patilswapnilv Shortcodely
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/08ef43cc-42ea-43bd-a590-4f9b2c719491?source=cve
- plugins.trac.wordpress.org /browser/shortcodely/trunk/shortcodely.php#L118
- plugins.trac.wordpress.org /browser/shortcodely/tags/1.0.1/shortcodely.php#L118
- plugins.trac.wordpress.org /browser/shortcodely/trunk/shortcodely.php#L73
- plugins.trac.wordpress.org /browser/shortcodely/tags/1.0.1/shortcodely.php#L73
- plugins.trac.wordpress.org /browser/shortcodely/trunk/shortcodely.php#L92
- plugins.trac.wordpress.org /browser/shortcodely/tags/1.0.1/shortcodely.php#L92
Sources
- CVE List CVE-2026-6913
- NVD CVE-2026-6913
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.