Skip to main content
CVE-2025-9399VulnerabilityPublished

CVE-2025-9399: YiFang CMS · SQL Injection

Affects YiFang CMSSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
YiFang CMSAffected
  • =2.0.0
  • =2.0.1
  • =2.0.2
  • =2.0.3
  • =2.0.4
  • =2.0.5
Fixed in–

AI-suggested

1. Immediate mitigation should include implementing web application firewall (WAF) rules to detect and block SQL injection patterns targeting the 'new_url' parameter, tailored to the specific request signatures of YiFang CMS. 2. Conduct thorough input validation and sanitization on all user-supplied inputs, especially the 'new_url' argument, using parameterized queries or prepared statements if source code access is available. 3. Restrict database user permissions to the minimum necessary to limit the impact of any injection attack. 4. Monitor web server and database logs for suspicious query patterns or anomalies indicative of injection attempts. 5. If feasible, isolate affected CMS instances behind VPN or internal networks to reduce exposure. 6. Engage with the vendor or community to obtain or develop patches or upgrade to a non-vulnerable version once available. 7. Perform regular security assessments and penetration testing focused on injection vulnerabilities. 8. Educate developers and administrators on secure coding practices to prevent similar issues in future deployments.

Description

A vulnerability was detected in YiFang CMS up to 2.0.5. Affected by this issue is some unknown functionality of the file app/logic/L_tool.php. The manipulation of the argument new_url results in sql injection. The attack may be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…