CVE-2025-26047: Loggrove v1.0 is vulnerable to SQL Injection in the read.py file.
CVE-2025-26047 is a medium-severity flaw (CVSS 5.1) affecting loggrove. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Loggrove v1.0 is vulnerable to SQL Injection in the read.py file.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 5.1 (Medium) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 88%) |
| CISA exploited list | No |
| Weakness | CWE-89 |
| Published | 2025-02-28 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-26047?
loggrove: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2025-26047 being exploited?
CVE-2025-26047 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-26047 affect?
CVE-2025-26047 affects loggrove. Severity is medium (CVSS 5.1). Loggrove v1.0 is vulnerable to SQL Injection in the read.py file.
How urgent is CVE-2025-26047?
Priority 26/100. Public exploit reference
Related CVEs
- CVE-2025-26014 CRITICAL 9.8 DOWNGRADE A Remote Code Execution (RCE) vulnerability in Loggrove v.1.0 allows a remote attacker to execute arbitrary co
- CVE-2025-26013 HIGH 8.2 DOWNGRADE An issue in Loggrove v.1.0 allows a remote attacker to obtain sensitive information via the read.py component.