Post Snippets <= 3.1.3 - Cross-Site Request Forgery to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 3.1.4
- Affected Plugin
- Post Snippets – Custom WordPress Code Snippets Customizer
- Affected Version
<= 3.1.3- CVSS
- 9.6Critical
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2021-25010
At a glance
CVE-2021-25010 is a critical-severity Cross-Site Request Forgery (CSRF) vulnerability in the Post Snippets WordPress plugin, affecting versions <= 3.1.3. It carries a CVSS score of 9.6 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.1.4; sites on affected versions should update now. Disclosed January 2022, reported by Muhammad Adel.
Vulnerability Overview
The Post Snippets WordPress plugin before 3.1.4 does not have CSRF check when importing files, allowing attacker to make a logged In admin import arbitrary snippets. Furthermore, imported snippers are not sanitised and escaped, which could lead to Stored Cross-Site Scripting issues
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Post Snippets <= 3.1.3 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Post Snippets the fix is 3.1.4: builds <= 3.1.3 are affected, anything from 3.1.4 onward is not.
Remediation
Update to version 3.1.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Post Snippets: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Post Snippets 3.1.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Post Snippets – Custom WordPress Code Snippets Customizer
- 8.8CVE-2026-56049: Post Snippets RCE
CVE-2026-56049 - 8.8CVE-2026-25001: Post Snippets RCE
CVE-2026-25001 - 8.8Freemius SDK <= 2.2.3 Arbitrary Options Update
- 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999 - 4.4CVE-2026-7430: Post Snippets <= 4.0.19 Stored Cross-Site Scripting
CVE-2026-7430 - 4.4CVE-2023-25459: Post Snippets <= 4.0.2 Stored Cross-Site Scripting
CVE-2023-25459
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C