FKIE_CVE-2024-48176
Vulnerability from fkie_nvd - Published: 2024-11-05 23:15 - Updated: 2025-05-01 15:00
Severity ?
Summary
Lylme Spage v1.9.5 is vulnerable to Incorrect Access Control. There is no limit on the number of login attempts, and the verification code will not be refreshed after a failed login, which allows attackers to blast the username and password and log into the system backend.
References
| URL | Tags | ||
|---|---|---|---|
| cve@mitre.org | https://gist.github.com/Gryffinbit/c0b37c6caae4844d4f59368e454d3e46 | Third Party Advisory |
Impacted products
| Vendor | Product | Version | |
|---|---|---|---|
| lylme | lylme_spage | 1.9.5 |
{
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:lylme:lylme_spage:1.9.5:*:*:*:*:*:*:*",
"matchCriteriaId": "2B5D86CA-58F2-4545-9D9D-0BA9967C9506",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Lylme Spage v1.9.5 is vulnerable to Incorrect Access Control. There is no limit on the number of login attempts, and the verification code will not be refreshed after a failed login, which allows attackers to blast the username and password and log into the system backend."
},
{
"lang": "es",
"value": "Lylme Spage v1.9.5 es vulnerable a un control de acceso incorrecto. No hay l\u00edmite en la cantidad de intentos de inicio de sesi\u00f3n y el c\u00f3digo de verificaci\u00f3n no se actualizar\u00e1 despu\u00e9s de un inicio de sesi\u00f3n fallido, lo que permite a los atacantes obtener el nombre de usuario y la contrase\u00f1a e iniciar sesi\u00f3n en el backend del sistema."
}
],
"id": "CVE-2024-48176",
"lastModified": "2025-05-01T15:00:20.730",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
},
"published": "2024-11-05T23:15:04.470",
"references": [
{
"source": "cve@mitre.org",
"tags": [
"Third Party Advisory"
],
"url": "https://gist.github.com/Gryffinbit/c0b37c6caae4844d4f59368e454d3e46"
}
],
"sourceIdentifier": "cve@mitre.org",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-863"
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…