The EthPress – Web3 Login plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 2.3.5. This is due to the verify_login() function in app/Login.php containing a missing return statement in the signature verification failure branch — when Signature::verify2() reports a mismatch, the function only assigns a WP_Error to a local variable and continues executing, causing unconditional fall-through to the login block where Address::log_in() calls wp_set_auth_cookie() regardless of whether the submitted signature is valid. This makes it possible for unauthenticated attackers to log in as any WordPress user who has a linked wallet address — including administrators — by submitting that user's public wallet address alongside an arbitrary well-formed signature, enabling full site takeover.
CVE-2026-19125
This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(low)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
References (6)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/ethpress/tags/2.3.5/app/Address.php#L419
- security@wordfencehttps://plugins.trac.wordpress.org/browser/ethpress/tags/2.3.5/app/Login.php#L46
- security@wordfencehttps://plugins.trac.wordpress.org/browser/ethpress/tags/2.3.5/app/Login.php#L51
- security@wordfencehttps://plugins.trac.wordpress.org/browser/ethpress/tags/2.3.5/app/Plugin.php#L75
- security@wordfencehttps://plugins.trac.wordpress.org/changeset/3683106/ethpress/trunk/app/Login.php
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/267acbd7-379c-4930-aa85-3071dfcac5a5?source=cve
Vendor Advisories for CVE-2026-19125(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 22:23 UTCEG score recompute
- 2026-09-23 21:33 UTCEG score recompute
- 2026-09-23 21:33 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-287
Frequently asked(4)
What is CVE-2026-19125?
When was CVE-2026-19125 disclosed?
What is the CVSS score of CVE-2026-19125?
How do I remediate CVE-2026-19125?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-19125
Is Your Infrastructure Affected by CVE-2026-19125?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.