CVE-2025-1642
Modernasistemas Modernanet ≤ 1.1.1
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-1642 is a medium-severity Resource Injection (CWE-99) vulnerability in Modernasistemas Modernanet. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 49th 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 SI-10 (Information Input Validation) 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-1642 is a critical vulnerability in Benner ModernaNet versions up to 1.1.0, affecting unknown code in the file /AGE0000700/GetImageMedico?fooId=1. The issue stems from improper control of resource identifiers (CWE-99, NVD-CWE-Other), triggered by manipulation of the fooId argument. It has a CVSS v3.1 base score of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), indicating medium severity with network accessibility and low attack complexity.
A remote attacker with low privileges (PR:L) can exploit this vulnerability without user interaction. Successful exploitation allows limited disclosure of confidential information (C:L), such as unauthorized access to resources via injected identifiers, but does not impact integrity or availability.
VulDB advisories recommend upgrading to Benner ModernaNet version 1.1.1 to address the issue. Additional details are available in the referenced sources, including https://github.com/yago3008/cves, https://vuldb.com/?ctiid.296692, https://vuldb.com/?id.296692, and https://vuldb.com/?submit.499877.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-4255
Vulnerability Data
A vulnerability was found in Benner ModernaNet up to 1.1.0. It has been declared as critical. This vulnerability affects unknown code of the file /AGE0000700/GetImageMedico?fooId=1. The manipulation of the argument fooId leads to improper control of resource identifiers. The attack…
more
can be initiated remotely. Upgrading to version 1.1.1 is able to address this issue. It is recommended to upgrade the affected component.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.8V1.3.9V1.3.11V9.2.2
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of inputs before they are accepted as resource identifiers.
Enforces authorizations on resource access so an injected identifier cannot reach outside the intended sphere.
Enforces information flow rules that block use of untrusted identifiers to reach unauthorized resources.
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 require input validation and sanitization that prevent resource-identifier injection flaws.
Least-privilege access policy and enforcement limits damage from injected resource identifiers even when input validation is absent.
Network segmentation and unauthorized-access controls reduce the blast radius of successful resource injection.
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.
Security testing can detect resource-injection flaws but does not itself implement preventive controls.
Secure SDLC mandates input validation and resource-identifier sanitization that directly prevents resource injection.
Application security requirements explicitly call for controls on external identifiers used to access resources.
Secure architecture principles reduce attack surface for resource injection but do not prescribe identifier validation.
Secure coding standards require strict validation and whitelisting of all resource identifiers before use.
Information-access-restriction policies limit which resources can be referenced, indirectly reducing injection impact.