CVE-2025-6895 json
MelaPress Login Security 2.1.0 - 2.1.1 - Authentication Bypass to Privilege Escalation via get_valid_user_based_on_token Function
published last yr. modified 4mo ago also EUVD-2025-22769
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
The Melapress Login Security plugin for WordPress is vulnerable to Authentication Bypass due to missing authorization within the get_valid_user_based_on_token() function in versions 2.1.0 to 2.1.1. This makes it possible for unauthenticated attackers who know an arbitrary user meta value to bypass authentication checks and log in as that user.
Patch / fix
- melapress melapress_login_security 2.2.0
Is CVE-2025-6895 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- melapress Melapress Login Security
Classification
- Weakness
-
- CWE-288 Authentication Bypass Using an Alternate Path or Channel
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/6f65d5c4-6f53-4836-9130-c9f4ed3be893?source=cve
- wordpress.org /plugins/melapress-login-security/#developers
- plugins.trac.wordpress.org /browser/melapress-login-security/tags/2.1.1/app/class-melapress-login-security.php
- plugins.trac.wordpress.org /browser/melapress-login-security/tags/2.1.1/app/modules/temporary-logins/class-temporary-logins.php
- plugins.trac.wordpress.org /changeset/3328137
Sources
- CVE List CVE-2025-6895
- NVD CVE-2025-6895
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.