CVE-2025-10787VulnerabilityPublished 22 Sep 2025

CVE-2025-10787: MuYuCMS · Server-Side Request Forgery

Affects MuYuCMSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 08:30 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 25% 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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
MuYuCMS	Affected =2.0 =2.1 =2.2 =2.3 =2.4 =2.5 =2.6 =2.7	Fixed in–

AI-suggested

Given the absence of official patches, European organizations should implement the following specific mitigations: 1) Immediately audit and restrict the 'Add Friend Link' functionality, disabling it if not essential, or applying strict input validation and sanitization on the 'Link URL' parameter to prevent arbitrary URLs. 2) Implement network-level egress filtering on the CMS server to restrict outbound HTTP/HTTPS requests only to trusted destinations, preventing SSRF exploitation from reaching internal or sensitive endpoints. 3) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious SSRF patterns targeting the vulnerable parameter. 4) Monitor server logs for unusual outbound requests or access patterns indicative of SSRF attempts. 5) Isolate the CMS server within a segmented network zone with minimal access to internal resources and sensitive services. 6) Plan for prompt patching once an official update becomes available from MuYuCMS developers. 7) Conduct internal penetration testing to identify any additional SSRF or related vulnerabilities. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable component and practical network controls to reduce exploitation risk.

Description

A vulnerability was found in MuYuCMS up to 2.7. Impacted is an unknown function of the file /index/index.html of the component Add Fiend Link Handler. Performing manipulation of the argument Link URL results in server-side request forgery. The attack may be initiated remotely. The exploit has been made public and could be used.

Impact

For European organizations using MuYuCMS, this vulnerability poses a moderate risk. SSRF attacks can allow attackers to bypass perimeter defenses and access internal network resources that are otherwise inaccessible externally. This could lead to exposure of sensitive internal services, unauthorized data access, or pivoting to more critical systems. Organizations hosting MuYuCMS on cloud infrastructure may be particularly at risk if the SSRF can be used to query cloud metadata services, potentially exposing credentials or configuration data. The medium severity rating suggests that while immediate damage may be limited, the vulnerability could be exploited as part of a multi-stage attack chain. European entities relying on MuYuCMS for web content management should be aware that attackers could leverage this flaw to gather intelligence about internal network topology or to launch further attacks against internal systems. The absence of known exploits in the wild reduces immediate urgency but does not eliminate risk, especially given the public disclosure of the vulnerability details. The impact is more pronounced for organizations with sensitive internal services behind the CMS server or those lacking network segmentation and strict egress filtering.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Sep 2025, 07:03 UTC

Technical details

References

Community reviews

Related threats