VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

anchorcms/anchor-cms: vulnerability history, versions and safety

anchorcms/anchor-cms is a package in the Packagist ecosystem. Vulert records 5 vulnerabilities for it across 14 releases, from Jan 2022 to Mar 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C1 H1 M3
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all anchorcms/anchor-cms vulnerabilities

Vulert verdict on anchorcms/anchor-cms i

Updated on 23 Oct 2026

Careful: 4 of the 5 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 5 vulnerabilities on record across 2 years, none in the last year.

What to do: Plan around the 4 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 2 years · 0 in the last year i
  • Latest disclosure 22 Mar 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 4 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for anchorcms/anchor-cms, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
0.12.7 H1 M3 No Details →
0.12.6 C1 H1 M3 No Details →
0.12.3 C1 H1 M3 No Details →
0.12.3a C1 H1 M3 No Details →
0.12.1 C1 H1 M3 No Details →
0.12 C1 H1 M3 No Details →
0.11 C1 H1 M3 No Details →
0.9.3.1-a C1 H1 M3 No Details →
0.9.3 C1 H1 M3 No Details →
0.9.3-b C1 H1 M3 No Details →
0.9.3-a C1 H1 M3 No Details →
0.9.2 C1 H1 M3 No Details →
0.9.1 C1 H1 M3 No Details →
0.9 C1 H1 M3 No Details →

Newest 14 of 14 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3
  • 2024 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for anchorcms/anchor-cms

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-7251: Anchor CMS Logs Credentials 9.8 critical 0.12.7 13 May 2022
CVE-2024-29338: Cross-Site Request Forgery in Anchor CMS 7.4 medium No fix published 22 Mar 2024
CVE-2024-29499: Cross-Site Request Forgery in Anchor CMS 7.4 high No fix published 22 Mar 2024
CVE-2021-44116: Cross-site Scripting in Anchor CMS 6.1 medium No fix published 05 Jan 2022
CVE-2022-25576: Cross-Site Request Forgery in Anchor CMS 4.5 medium No fix published 26 Mar 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About anchorcms/anchor-cms

Is anchorcms/anchor-cms safe to use?

Vulert records 5 vulnerabilities for anchorcms/anchor-cms in Packagist: 1 critical, 1 high, 3 medium and 0 low. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does anchorcms/anchor-cms have?

5 vulnerabilities are recorded for anchorcms/anchor-cms in the Packagist ecosystem: 1 critical, 1 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new anchorcms/anchor-cms vulnerabilities disclosed?

0 vulnerabilities were recorded for anchorcms/anchor-cms in the last 12 months, and the oldest entry in this database dates to 05 Jan 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of anchorcms/anchor-cms are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor anchorcms/anchor-cms for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the anchorcms/anchor-cms version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.