CVE-2025-60954 json
Microweber CMS 2.0 has Weak Password Requirements.
published last yr. modified 4d ago also EUVD-2025-35888
- cvss
- 8.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
Microweber CMS 2.0 has Weak Password Requirements. The application does not enforce minimum password length or complexity during password resets. Users can set extremely weak passwords, including single-character passwords, which can lead to account compromise, including administrative accounts.
Is CVE-2025-60954 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
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gist.github.com https://gist.github.com/progprnv/feae2b76f2db0cb2ac6e14b1bf7d8646 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/progprnv/CVE-Reports/blob/main/CVE-2025-60954 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L |
| CNA | 3.1 | 8.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L |
Classification
- Weakness
-
- CWE-521 Weak Password Requirements
References
-
gist.github.com
/progprnv/feae2b76f2db0cb2ac6e14b1bf7d8646
exploit, third-party-advisory
-
github.com
/progprnv/CVE-Reports/blob/main/CVE-2025-60954
exploit, third-party-advisory
-
github.com
/microweber/microweber
product
Sources
- CVE List CVE-2025-60954
- NVD CVE-2025-60954
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.