Cyber Resilience

CVE-2025-9797

Published
01 September 2025
Modified
17 June 2026
CVSS Score v4 1.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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:X
EPSS Score 0.0025 16th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2025-9797 is a low-severity Injection (CWE-74) vulnerability. Its CVSS base score is 1.9 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-7 (Software, Firmware, and Information Integrity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

A vulnerability was determined in mrvautin expressCart up to b31302f4e99c3293bd742c6d076a721e168118b0. This impacts an unknown function of the file /admin/product/edit/ of the component Edit Product Page. This manipulation causes injection. The attack can be initiated remotely. The exploit has been publicly…

more

disclosed and may be utilized. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

CWE(s)
CWE-74CWE-707

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
Why these techniques?

Generic injection flaw on web admin page directly maps to content injection technique; vague description and admin context limit certainty on other mappings like T1190.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-41237Shared CWE-74
CVE-2026-10223Shared CWE-707, CWE-74
CVE-2026-10729Shared CWE-74
CVE-2026-0972Shared CWE-74
CVE-2026-10222Shared CWE-707, CWE-74
CVE-2026-1154Shared CWE-74
CVE-2025-0697Shared CWE-707, CWE-74
CVE-2026-0865Shared CWE-74
CVE-2025-1611Shared CWE-707, CWE-74
CVE-2026-2954Shared CWE-707, CWE-74

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • AC-3 Access Enforcement
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.3.9
  • V1.2.1
  • V1.2.3
  • V1.2.5

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match
prevent

Directly requires validation and neutralization of all inputs to the product edit endpoint, blocking the CWE-74 injection vectors described in the CVE.

SI-7 Software, Firmware, and Information Integrity partial match
detect

Verifies integrity of application code and data after edits, detecting unauthorized changes resulting from successful injection.

AC-3 Access Enforcement minimal match
prevent

Enforces access restrictions on the /admin/product/edit/ page so that only authorized administrators can reach the vulnerable function.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and output encoding that prevent injection flaws.

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.

A.8.28 Secure coding mostly match
prevents

Secure coding standards directly require proper neutralization of inputs and outputs, eliminating CWE-707.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development catches injection vulnerabilities before release.

A.8.15 Logging partial match
detects

Logging supports detection of injection attempts but does not prevent the weakness.

A.8.16 Monitoring activities partial match
detects

Monitoring activities can identify active injection attacks after they occur.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection attacks in software design.

References