CVE-2026-7430 json
Post Snippets <= 4.0.19 - Authenticated (Administrator+) Stored Cross-Site Scripting via Import
published 2026-05-29 5 mo ago modified 2026-07-21 3 mo ago also EUVD-2026-33246
- cvss
- 4.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 15%
- public exploits
- 0
- none known
Summary
The Post Snippets plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 4.0.19. This is due to insufficient output escaping of imported snippet content when rendering JavaScript variables in the post editor. Specifically, the `jqueryUiDialog()` method in `WPEditor.php` embeds snippet content directly into JavaScript string literals without escaping double quotes (the quote-escaping code on line 214 is commented out). When snippets are imported via the Import/Export feature, the content bypasses WordPress's `wp_magic_quotes()` (which would otherwise add protective backslashes), allowing double quotes in snippet content to break out of the JavaScript string context. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts via a malicious import file that execute whenever any administrator accesses a post editor page. Please note that this does not affect single-site installations as administrators already have the `unfiltered_html` capability.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N |
Affected products
- saadiqbal Post Snippets – Custom WordPress Code Snippets Customizer
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/59dc2448-491c-478f-a784-c727057b126b?source=cve
- plugins.trac.wordpress.org /browser/post-snippets/tags/4.0.19/src/PostSnippets/WPEditor.php#L218
- plugins.trac.wordpress.org /browser/post-snippets/trunk/src/PostSnippets/WPEditor.php#L218
- plugins.trac.wordpress.org /browser/post-snippets/tags/4.0.19/src/PostSnippets/DBTable.php#L114
- plugins.trac.wordpress.org /browser/post-snippets/trunk/src/PostSnippets/DBTable.php#L114
- plugins.trac.wordpress.org /browser/post-snippets/tags/4.1.1/src/PostSnippets/WPEditor.php#L20
- plugins.trac.wordpress.org /browser/post-snippets/tags/4.1.1/src/PostSnippets/WPEditor.php#L221
- plugins.trac.wordpress.org /browser/post-snippets/tags/4.1.1/src/PostSnippets/WPEditor.php#L227
Sources
- CVE List CVE-2026-7430
- NVD CVE-2026-7430
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.