Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.5

Cross-Site Request Forgery in Anchor CMS

CVE-2022-25576GHSA-322v-p3jc-7hrg

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist anchorcms/anchor-cms

    Affected
    <= 0.12.7
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.5 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N
EPSS
  • CVE-2022-25576: 0.40% estimated exploitation activity in the next 30 days; percentile 34.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Anchor CMS v0.12.7 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component anchor/routes/posts.php. This vulnerability allows attackers to arbitrarily delete posts.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-322v-p3jc-7hrg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-25576

Advisory: Cross-Site Request Forgery in Anchor CMS
IDs: CVE-2022-25576, GHSA-322v-p3jc-7hrg
Record: https://patchnext.com/advisories/cve-2022-25576 (revision 1, source checked 26 Oct 2026, 13:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist anchorcms/anchor-cms: affected <= 0.12.7

## Suggested inspection (read-only)
- Packagist anchorcms/anchor-cms: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on anchorcms/anchor-cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-322v-p3jc-7hrg (GitHub-reviewed advisory GHSA-322v-p3jc-7hrg lists affected ranges: Packagist anchorcms/anchor-cms >=0 <=0.12.7)

Commands are suggestions: review each one before running it.

Loading voting…