CVE-2026-4082 json
ER Swiffy Insert <= 1.0.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes
published 2026-04-22 6 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-24648
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
The ER Swiffy Insert plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the [swiffy] shortcode in all versions up to and including 1.0.0. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes ('n', 'w', 'h'). These attributes are extracted using extract() and directly interpolated into the HTML output without any escaping such as esc_attr(). 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
- 6 mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% 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
- erithq ER Swiffy Insert
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/074d9712-9b26-47da-9e24-49854fd7257c?source=cve
- plugins.trac.wordpress.org /browser/er-swiffy-insert/trunk/er-swiffy-insert.php#L56
- plugins.trac.wordpress.org /browser/er-swiffy-insert/tags/1.0.0/er-swiffy-insert.php#L56
- plugins.trac.wordpress.org /browser/er-swiffy-insert/trunk/er-swiffy-insert.php#L49
- plugins.trac.wordpress.org /browser/er-swiffy-insert/tags/1.0.0/er-swiffy-insert.php#L49
Sources
- CVE List CVE-2026-4082
- NVD CVE-2026-4082
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.