CVE-2024-47059 json
Users enumeration - weak password login
published 2y ago modified 4mo ago also GHSA-8vff-35qm-qjvv , EUVD-2024-2755
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
When logging in with the correct username and incorrect weak password, the user receives the notification, that their password is too weak.
However when an incorrect username is provided alongside with a weak password, the application responds with ’Invalid credentials’ notification.
This difference could be used to perform username enumeration.
Patch / fix
- packagist mautic/core 5.1.1
- Mautic Mautic < 5.1.1, 5.1.1
Is CVE-2024-47059 in your dependencies? 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
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | mautic/core | >=5.1.0, <5.1.1 |
5.1.1 |
Affected products
- Mautic Mautic
Classification
References
-
github.com
/mautic/mautic/security/advisories/GHSA-8vff-35qm-qjvv
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-47059
advisory
-
github.com
/mautic/mautic
package
Sources
- CVE List CVE-2024-47059
- GitHub Advisory GHSA-8vff-35qm-qjvv
- NVD CVE-2024-47059
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.