CVE-2026-25812
CSRF in PlaciPy 1.0.0 enables unauthorized actions via credentialed CORS.
Is CVE-2026-25812 being exploited?
Not confirmed. CVE-2026-25812 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-25812?
CVE-2026-25812 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-25812?
Yes. A fix has been recorded for CVE-2026-25812. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-25812 affect?
CVE-2026-25812 affects PlaciPy v1.0.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-25812?
Add CSRF protections; enable SameSite cookies; disable credentialed CORS; patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows authenticated users to be tricked into performing state-changing actions through CSRF in CORS-enabled requests.
Patch when possible
- affected= 1.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.