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

CVE-2025-25426 has a CVSS 3.1 base score of 7.2 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Yshopmall are affected by CVE-2025-25426?

CVE-2025-25426 presents moderate security risk, a SQL injection vulnerability rated CVSS 7.2.

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

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

How to fix or mitigate CVE-2025-25426?

Within 7 days: Identify all affected systems and apply vendor patches promptly. Validate that input sanitization is in place for all user-controlled parameters.

Yshopmall CVE-2025-25426

HIGH

SQL Injection (CWE-89)

2025-03-04 cve@mitre.org

SQLi Yshopmall Guchengwuyue

7.2

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.2 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:29 vuln.today

PoC Detected

Jun 12, 2025 - 20:34 vuln.today

Public exploit code

CVE Published

Mar 04, 2025 - 22:15 nvd

HIGH 7.2

DescriptionCVE.org

yshopmall <=v1.9.0 is vulnerable to SQL Injection in the image listing interface.

AnalysisAI

yshopmall <=v1.9.0 is vulnerable to SQL Injection in the image listing interface. Rated high severity (CVSS 7.2), this vulnerability is remotely exploitable, 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. yshopmall <=v1.9.0 is vulnerable to SQL Injection in the image listing interface. Affected products include: Guchengwuyue Yshopmall.

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.