CVE-2018-20231: Cross Site Request Forgery (CSRF) in the two-factor-authentication plugin before 1.3.13 for WordPress allows r

Q: How do I fix CVE-2018-20231?

two-factor-authentication: upgrade to 1.3.13. Exact commands for each OS are on this page.

Q: Is CVE-2018-20231 being exploited?

CVE-2018-20231 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-20231 affect?

CVE-2018-20231 affects two-factor-authentication. Severity is high (CVSS 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.

Q: How urgent is CVE-2018-20231?

Priority 54/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2018-20231 is a high-severity flaw (CVSS 8.8) affecting two-factor-authentication. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.4% (top 27%)
CISA exploited list	No
Weakness	CWE-352
Published	2018-12-19
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: simbahosting

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-12-19 11:29 UTCPublished CVE record published
2026-06-17 01:52 UTCUpdated Record last modified

simbahosting two-factor-authentication UPGRADE

Affected: < 1.3.13

Fixed in: 1.3.13

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy two-factor-authentication || rpm -q two-factor-authentication || two-factor-authentication --version

2. UPGRADE to 1.3.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade two-factor-authentication

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade two-factor-authentication

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-20231?

two-factor-authentication: upgrade to 1.3.13. Exact commands for each OS are on this page.

Is CVE-2018-20231 being exploited?

CVE-2018-20231 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-20231 affect?

CVE-2018-20231 affects two-factor-authentication. Severity is high (CVSS 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.

How urgent is CVE-2018-20231?

Priority 54/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2015-9355 MEDIUM 6.1 UPGRADE The two-factor-authentication plugin before 1.1.10 for WordPress has XSS in the admin area.

References

← Back to latest CVEs