Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NSummary
CVE-2025-26013 is a high-severity Inclusion of Sensitive Information in Source Code (CWE-540) vulnerability in Olajowon Loggrove. Its CVSS base score is 8.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Code Repositories (T1213.003); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-26013 is an information disclosure vulnerability in Loggrove version 1.0, specifically within the read.py component. Published on 2025-02-21, the issue enables a remote attacker to obtain sensitive information. It carries a CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N) and is classified under CWE-540.
The vulnerability can be exploited by any remote attacker over the network, requiring low attack complexity, no privileges, and no user interaction. Successful exploitation grants high-impact access to sensitive information, with a low integrity impact but no effect on availability.
Mitigation details are available in the referenced advisory at https://gitee.com/olajowon/loggrove/issues/IBJSXS.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-4483
Vulnerability Data
An issue in Loggrove v.1.0 allows a remote attacker to obtain sensitive information via the read.py component.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis locate hard-coded sensitive values before code is deployed.
Enforces access so that source containing embedded secrets cannot be reached by unauthorized parties.
Engineering principles require secrets to be externalized rather than embedded in source.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prohibit embedding secrets or sensitive data in source code.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Directly restricts access to source code, preventing exposure of embedded sensitive information.
Secure coding standards explicitly prohibit hard-coding credentials or sensitive data.
Classification helps identify source code containing sensitive data so it can be protected.
Access control limits who can view or retrieve source code that may contain secrets.
Secure SDLC practices include removing secrets from code before commit or deployment.
Environment separation reduces risk of accidental exposure but does not address secrets already in code.