CVE-2018-20231

CVE-2018-20231 is a high-severity vulnerability in Simbahosting Two-factor-authentication with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Description

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.

Frequently asked questions

What is CVE-2018-20231?
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 severe is CVE-2018-20231?
CVE-2018-20231 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-20231 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-20231?
CVE-2018-20231 affects Simbahosting Two-factor-authentication. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-20231?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-20231 published?
CVE-2018-20231 was published on 2018-12-19 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Simbahosting Two-factor-authentication

All CVEs affecting Simbahosting Two-factor-authentication →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →