What is the CVSS score of CVE-2025-26047?

CVE-2025-26047 has a CVSS 3.1 base score of 5.1 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of Loggrove are affected by CVE-2025-26047?

Organizations using Loggrove v1.0 should be aware of moderate risk from CVE-2025-26047, a SQL injection vulnerability rated CVSS 5.1.

Is there a public PoC exploit available for CVE-2025-26047?

Yes, a public proof-of-concept exploit is available for CVE-2025-26047. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2025-26047?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Validate input sanitization for user-controlled parameters.

Loggrove CVE-2025-26047

MEDIUM

SQL Injection (CWE-89)

2025-02-28 cve@mitre.org

SQLi Loggrove Olajowon

5.1

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.1 MEDIUM

AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:29 vuln.today

PoC Detected

Jun 12, 2025 - 20:17 vuln.today

Public exploit code

CVE Published

Feb 28, 2025 - 16:15 nvd

MEDIUM 5.1

DescriptionCVE.org

Loggrove v1.0 is vulnerable to SQL Injection in the read.py file.

AnalysisAI

Loggrove v1.0 is vulnerable to SQL Injection in the read.py file. Rated medium severity (CVSS 5.1), this vulnerability is no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as SQL Injection (CWE-89), which allows attackers to execute arbitrary SQL commands against the database. Loggrove v1.0 is vulnerable to SQL Injection in the read.py file. Affected products include: Olajowon Loggrove.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use parameterized queries/prepared statements. Never concatenate user input into SQL. Apply least-privilege database permissions.