CVE-2024-25187VulnerabilityPublished 2 Apr 2024Updated 28 Aug 2024

CVE-2024-25187: 71cms · n/a

Affects 71cmsSource CVE Database V5

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 on the impacted component.
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 impacted component 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 impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Apr 2024
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
GitHubxiaocheng-keji/71cms`pkg:github/xiaocheng-keji/71cms`Other threats	Affected =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict access to the getweather.html endpoint by implementing web application firewall (WAF) rules or server-side access controls to block unauthorized requests. 2. Employ network segmentation and firewall rules to limit the CMS server's ability to make outbound HTTP requests to internal or sensitive services. 3. Monitor outbound traffic from the CMS server for unusual or unexpected requests that may indicate exploitation attempts. 4. If possible, disable or remove the getweather.html functionality if it is not essential to operations. 5. Conduct thorough code review and input validation on any server-side request functionality to ensure URLs or parameters cannot be manipulated to access internal resources. 6. Stay alert for official patches or updates from 71cms developers and apply them promptly once available. 7. Implement intrusion detection systems (IDS) tuned to detect SSRF attack patterns targeting the CMS. 8. Educate security teams about SSRF risks and ensure incident response plans include SSRF scenarios. These steps go beyond generic advice by focusing on network-level controls, monitoring, and disabling vulnerable features where feasible.

Description

Server Side Request Forgery (SSRF) vulnerability in 71cms v1.0.0, allows remote unauthenticated attackers to obtain sensitive information via getweather.html.

Impact

The primary impact of CVE-2024-25187 is unauthorized disclosure of sensitive information due to the SSRF vulnerability. Attackers can exploit this flaw to access internal services, metadata endpoints, or other protected resources that are normally inaccessible externally. This can lead to leakage of confidential data such as internal IP addresses, configuration details, or credentials stored in internal services. Although the vulnerability has limited direct impact on data integrity or system availability, the information gained can facilitate further attacks, including privilege escalation or lateral movement within the network. Organizations relying on 71cms v1.0.0 risk exposure of internal infrastructure details, which can compromise overall security posture. The ease of exploitation without authentication or user interaction increases the likelihood of automated scanning and exploitation attempts. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as public proof-of-concept code could emerge. The impact is particularly severe for organizations with sensitive internal services accessible from the vulnerable CMS server.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 10:30 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats