CVE-2018-20231

HIGHNVD 8.88.8—

8.8

Cross Site Request Forgery (CSRF) in the two-factor-authentication plugin before 1.3.13 for WordPress allows remote attackers to disable 2FA via the tfa_enable_tfa parameter due to missing nonce validation.

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

Published

December 19, 2018

Last Modified

November 21, 2024

References (6)

cve@mitrehttps://wordpress.org/plugins/two-factor-authentication/#developers
cve@mitrehttps://wpvulndb.com/vulnerabilities/9187
cve@mitrehttps://www.privacy-wise.com/two-factor-authentication-cross-site-request-forgery-csrf-vulnerability-cve-2018-20231/
af854a3a-2127-422b-91ae-364da2661108https://wordpress.org/plugins/two-factor-authentication/#developers
af854a3a-2127-422b-91ae-364da2661108https://wpvulndb.com/vulnerabilities/9187
af854a3a-2127-422b-91ae-364da2661108https://www.privacy-wise.com/two-factor-authentication-cross-site-request-forgery-csrf-vulnerability-cve-2018-20231/

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 10× 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-05 06:08 UTCepss_batch
2026-06-05 06:08 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 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 00:11 UTCEG score recompute
2026-05-28 00:11 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2018-20231?

CVE-2018-20231 is a high vulnerability published on December 19, 2018. Cross Site Request Forgery (CSRF) in the two-factor-authentication plugin before 1.3.13 for WordPress allows remote attackers to disable 2FA via the tfaenabletfa parameter due to missing nonce validation.

When was CVE-2018-20231 disclosed?

CVE-2018-20231 was first published in the National Vulnerability Database on December 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-20231 actively exploited?

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

What is the CVSS score of CVE-2018-20231?

CVE-2018-20231 has a CVSS v3 base score of 8.8 (NVD).

How do I remediate CVE-2018-20231?

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

Explore →

Is Your Infrastructure Affected by CVE-2018-20231?

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

Start Free Scan →Browse All CVEs

CVE-2018-20231

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-20231?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)