CVE-2019-6027

HIGHNVD 8.88.8—

8.8

Cross-site request forgery (CSRF) vulnerability in WP Spell Check 7.1.9 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.

CVSS v3: 8.8
EG Score: 8.8(medium)
EPSS: 31.5%
KEV: Not listed

Published

December 26, 2019

Last Modified

November 21, 2024

References (4)

vultures@jpcerthttp://jvn.jp/en/jp/JVN26838191/index.html
vultures@jpcerthttps://wordpress.org/plugins/wp-spell-check/
af854a3a-2127-422b-91ae-364da2661108http://jvn.jp/en/jp/JVN26838191/index.html
af854a3a-2127-422b-91ae-364da2661108https://wordpress.org/plugins/wp-spell-check/

Weakness Classification(1)

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

CWE-352Cross-Site Request Forgery (CSRF)

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-06 13:45 UTCepss_batch
2026-06-06 13:45 UTCepss_batch
2026-06-05 22:45 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 09:54 UTCEG score recompute

Frequently asked(5)

What is CVE-2019-6027?

CVE-2019-6027 is a high vulnerability published on December 26, 2019. Cross-site request forgery (CSRF) vulnerability in WP Spell Check 7.1.9 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.

When was CVE-2019-6027 disclosed?

CVE-2019-6027 was first published in the National Vulnerability Database on December 26, 2019, 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-2019-6027 actively exploited?

CVE-2019-6027 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-6027?

CVE-2019-6027 has a CVSS v3 base score of 8.8 (NVD).

How do I remediate CVE-2019-6027?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-6027, 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-2019-6027

Explore →

Is Your Infrastructure Affected by CVE-2019-6027?

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

Start Free Scan →Browse All CVEs

CVE-2019-6027

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-6027?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)