CVE-2018-7251

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 72.3%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 72%
CISA-KEV: Not listedEPSS: 72%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered in config/error.php in Anchor 0.12.3. The error log is exposed at an errors.log URI, and contains MySQL credentials if a MySQL error (such as "Too many connections") has occurred.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
78(Track*)
EG Risk 78/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation72% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.4%
KEV
Not listed

Published

February 19, 2018

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jun 22, 2026
Patch available. Sources: github_release.
generic

Tijme Gommers on X: "1. Register on PublicWWW (https://t.co/DpQp4rtYEj) 2. Go to https://t.co/1mc01HdhaM 3. Pick a random blog created with AnchorCMS 4. Go to that-blog[dot]com/anchor/errors.log 5. Press [ctrl] + [f] and search for "password" 6. Database access granted https://t.co/9JqxXQusLY" / X

https://twitter.com/finnwea/status/965279233030393856
github_release Patch Available

Security & Bugfixes

Patch available: anchorcms/anchor-cms 0.12.7

https://github.com/anchorcms/anchor-cms/releases/tag/0.12.7
generic

Issue · GitHub

https://github.com/anchorcms/anchor-cms/issues/1247

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
anchorcms/anchor-cms0.11 ... 0.9.3.1-a (13 versions)0.12.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:37 UTCEG score recompute
  2. 2026-07-22 22:17 UTCEG score recompute
  3. 2026-07-22 14:05 UTCEPSS rescore
  4. 2026-07-21 17:18 UTCOSV refresh
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-20 17:04 UTCEPSS rescore
  8. 2026-07-19 14:28 UTCEPSS rescore
  9. 2026-07-19 14:28 UTCEPSS rescore
  10. 2026-07-15 16:55 UTCEPSS rescore
  11. 2026-07-13 22:27 UTCEPSS rescore
  12. 2026-07-13 06:10 UTCEPSS rescore
  13. 2026-07-12 05:43 UTCEPSS rescore
  14. 2026-07-09 19:06 UTCEPSS rescore
  15. 2026-07-05 02:27 UTCEPSS rescore
  16. 2026-07-04 12:56 UTCOSV refresh
  17. 2026-07-04 06:28 UTCEPSS rescore
  18. 2026-07-04 06:28 UTCEPSS rescore
  19. 2026-07-01 15:03 UTCEPSS rescore
  20. 2026-07-01 15:03 UTCEPSS rescore
  21. 2026-06-28 14:04 UTCEPSS rescore
  22. 2026-06-27 03:06 UTCEPSS rescore
  23. 2026-06-27 03:06 UTCEPSS rescore
  24. 2026-06-25 13:47 UTCEPSS rescore
  25. 2026-06-25 13:47 UTCEPSS rescore
Show 23 more
  1. 2026-06-24 14:02 UTCEPSS rescore
  2. 2026-06-24 14:02 UTCEPSS rescore
  3. 2026-06-23 21:30 UTCEPSS rescore
  4. 2026-06-23 21:30 UTCEPSS rescore
  5. 2026-06-21 01:57 UTCEPSS rescore
  6. 2026-06-21 01:57 UTCEPSS rescore
  7. 2026-06-18 17:50 UTCEPSS rescore
  8. 2026-06-18 17:50 UTCEPSS rescore
  9. 2026-06-17 17:50 UTCEPSS rescore
  10. 2026-06-16 17:50 UTCEPSS rescore
  11. 2026-06-16 17:50 UTCEPSS rescore
  12. 2026-06-16 00:43 UTCOSV refresh
  13. 2026-06-15 17:45 UTCEPSS rescore
  14. 2026-06-13 22:58 UTCEPSS rescore
  15. 2026-06-11 13:57 UTCEPSS rescore
  16. 2026-06-10 22:16 UTCEPSS rescore
  17. 2026-06-08 14:14 UTCEPSS rescore
  18. 2026-06-05 22:45 UTCEPSS rescore
  19. 2026-06-05 22:45 UTCEPSS rescore
  20. 2026-05-31 00:14 UTCEPSS rescore
  21. 2026-05-31 00:14 UTCEPSS rescore
  22. 2026-05-28 11:13 UTCEG score recompute
  23. 2026-05-25 00:13 UTCOSV refresh

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-47459
    First seen Oct 3, 2019

    AnchorCMS < 0.12.3a - Information Disclosure

    Open source ↗
  • Nucleihttp/cves/2018/CVE-2018-7251.yaml
    First seen Jan 1, 2018

    Anchor CMS 0.12.3 - Error Log Exposure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-7251?
CVE-2018-7251 is a critical vulnerability published on February 19, 2018. An issue was discovered in config/error.php in Anchor 0.12.3. The error log is exposed at an errors.log URI, and contains MySQL credentials if a MySQL error (such as "Too many connections") has occurred.
When was CVE-2018-7251 disclosed?
CVE-2018-7251 was first published in the National Vulnerability Database on February 19, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-7251 actively exploited?
CVE-2018-7251 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-7251?
CVE-2018-7251 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-7251?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-7251, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-7251

Explore →

Is Your Infrastructure Affected by CVE-2018-7251?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs