CVE-2018-20231
UnknownEPSS 1.44%
Last modified
CVE-2018-20231 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.44% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Simbahosting | Two-Factor-Authentication | < 1.3.13 |
References
- https://wordpress.org/plugins/two-factor-authentication/#developersThird Party Advisory
- https://wpvulndb.com/vulnerabilities/9187Third Party Advisory
- https://www.privacy-wise.com/two-factor-authentication-cross-site-request-forgery-csrf-vulnerability-cve-2018-20231/Exploit, Third Party Advisory
- https://wordpress.org/plugins/two-factor-authentication/#developersThird Party Advisory
- https://wpvulndb.com/vulnerabilities/9187Third Party Advisory
- https://www.privacy-wise.com/two-factor-authentication-cross-site-request-forgery-csrf-vulnerability-cve-2018-20231/Exploit, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
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?
Severity scoring for CVE-2018-20231 is pending analysis. The EPSS model estimates a 1.44% probability of exploitation in the next 30 days.
How do I fix CVE-2018-20231?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2018
- CVE-2018-20225An issue was discovered in pip (all versions) because it ins…7.8
- CVE-2018-20226An organization administrator can add a super administrator …
- CVE-2018-20227RDF4J 2.4.2 allows Directory Traversal via ../ in an entry i…7.5
- CVE-2018-20228Subsonic V6.1.5 allows internetRadioSettings.view streamUrl …
- CVE-2018-20229GitLab Community and Enterprise Edition before 11.3.14, 11.4…
- CVE-2018-20230An issue was discovered in PSPP 1.2.0. There is a heap-based…
- CVE-2018-20232The labels widget gadget in Atlassian Jira before version 7.…
- CVE-2018-20233The Upload add-on resource in Atlassian Universal Plugin Man…
- CVE-2018-20234There was an argument injection vulnerability in Atlassian S…
- CVE-2018-20235There was an argument injection vulnerability in Atlassian S…
- CVE-2018-20236There was an command injection vulnerability in Sourcetree f…
- CVE-2018-20237Atlassian Confluence Server and Data Center before version 6…6.5
Are you affected by CVE-2018-20231?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST