CVE-2026-2723 json
Post Snippits <= 1.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting via Settings Update
published 2026-03-21 7 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-14152
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
The Post Snippits plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing nonce validation on the settings page handlers for saving, adding, and deleting snippets. This makes it possible for unauthenticated attackers to modify plugin settings and inject malicious scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- phy9pas Post Snippits
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/d96d1f33-43b3-4e20-967e-988cb32b04ee?source=cve
- plugins.trac.wordpress.org /browser/post-snippits/trunk/post-snippits.php#L55
- plugins.trac.wordpress.org /browser/post-snippits/tags/1.0/post-snippits.php#L55
- plugins.trac.wordpress.org /browser/post-snippits/trunk/post-snippits.php#L71
- plugins.trac.wordpress.org /browser/post-snippits/tags/1.0/post-snippits.php#L71
- plugins.trac.wordpress.org /browser/post-snippits/trunk/post-snippits.php#L77
- plugins.trac.wordpress.org /browser/post-snippits/tags/1.0/post-snippits.php#L77
Sources
- CVE List CVE-2026-2723
- NVD CVE-2026-2723
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.