Skip to main content
CVE-2025-7102VulnerabilityPublished

CVE-2025-7102: BoyunCMS · SQL Injection

Affects BoyunCMSSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 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 30% 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 7 Jul 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-25.

What to do

Affected software

ProductAffectedFixed in
BoyunCMSAffected
  • =1.4.0
  • =1.4.1
  • =1.4.2
  • =1.4.3
  • =1.4.4
  • =1.4.5
  • =1.4.6
  • =1.4.7
  • =1.4.8
  • =1.4.9
  • =1.4.10
  • =1.4.11
  • =1.4.12
  • =1.4.13
  • =1.4.14
  • =1.4.15
  • =1.4.16
  • =1.4.17
  • =1.4.18
  • =1.4.19
  • =1.4.20
Fixed in–

AI-suggested

1. Immediate mitigation should include restricting access to the vulnerable endpoint (application/update/controller/Server.php) via web application firewalls (WAFs) or network-level controls to limit exposure. 2. Implement input validation and parameterized queries or prepared statements in the affected code to prevent SQL injection. 3. Conduct thorough code audits of custom BoyunCMS deployments to identify and remediate similar injection points. 4. Enable detailed logging and monitoring of database queries and web requests to detect suspicious activity indicative of exploitation attempts. 5. Employ database user accounts with the least privileges necessary to limit the impact of any successful injection. 6. Regularly back up CMS data and test restoration procedures to minimize downtime and data loss in case of compromise. 7. Educate development and operations teams about secure coding practices and the risks of SQL injection vulnerabilities.

Description

A vulnerability was found in BoyunCMS up to 1.4.20. It has been declared as critical. This vulnerability affects unknown code of the file application/update/controller/Server.php. The manipulation of the argument phone leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…