Skip to main content
CVE-2025-7103VulnerabilityPublished

CVE-2025-7103: BoyunCMS · Server-Side Request Forgery

Affects BoyunCMSSource 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 31% 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-26.

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 upgrade: Organizations should upgrade BoyunCMS to a version beyond 1.4.20 once a patch is released that addresses this SSRF vulnerability. 2. Input validation: Implement strict server-side validation and sanitization of all user inputs that influence outbound HTTP requests, especially in the payment controller component. 3. Network segmentation: Restrict the server's ability to make outbound HTTP requests to only trusted and necessary endpoints using firewall rules or network ACLs. This limits the potential impact of SSRF exploitation. 4. Monitoring and logging: Enable detailed logging of outbound HTTP requests from the BoyunCMS server and monitor for unusual or unexpected request patterns that could indicate exploitation attempts. 5. Web application firewall (WAF): Deploy or update WAF rules to detect and block SSRF attack patterns targeting the vulnerable endpoint. 6. Access controls: Limit access to the BoyunCMS administrative and payment interfaces to trusted IP addresses or VPN users to reduce exposure. 7. Incident response readiness: Prepare to investigate and respond to potential SSRF exploitation attempts, including network traffic analysis and forensic review of server logs.

Description

A vulnerability was found in BoyunCMS up to 1.4.20. It has been rated as critical. This issue affects some unknown processing of the file /application/pay/controller/Index.php of the component curl. The manipulation leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…