VulnerabilityPublished 25 Jul 2025Updated 27 Jul 2025

CVE-2025-8133: yanyutao0402 ChanCMS · Server-Side Request Forgery

Affects yanyutao0402 ChanCMSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:16 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 33% 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 25 Jul 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
GitHubyanyutao0402/ChanCMS`pkg:github/yanyutao0402/ChanCMS`Other threats	Affected =3.1.0 =3.1.1 =3.1.2	Fixed in–

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

AI-suggested

European organizations should immediately upgrade ChanCMS installations to version 3.1.3 or later, which contains the official patch addressing this SSRF vulnerability. Beyond patching, organizations should implement strict input validation and sanitization on any user-supplied URLs or parameters to prevent SSRF. Network segmentation should be enforced to limit the web server's ability to access sensitive internal resources, minimizing the impact of any SSRF exploitation. Employing web application firewalls (WAFs) with rules designed to detect and block SSRF patterns can provide an additional layer of defense. Monitoring outbound traffic from web servers for unusual or unauthorized requests can help detect exploitation attempts early. Finally, conducting regular security assessments and code reviews focusing on external input handling will reduce the risk of similar vulnerabilities.

Description

A vulnerability classified as critical has been found in yanyutao0402 ChanCMS up to 3.1.2. This affects the function getArticle of the file app/modules/api/service/gather.js. The manipulation of the argument targetUrl leads to server-side request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 3.1.3 is able to address this issue. The identifier of the patch is 3ef58a50e8b3c427b03c8cf3c9e19a79aa809be6. It is recommended to upgrade the affected component.

Impact

For European organizations using ChanCMS versions 3.1.0 through 3.1.2, this SSRF vulnerability poses a moderate risk. Attackers exploiting this flaw could cause the affected server to initiate unauthorized requests to internal systems, potentially exposing sensitive internal services or data not intended for public access. This could lead to information disclosure or facilitate lateral movement within the network. The impact is somewhat limited by the medium CVSS score, indicating that while the vulnerability is exploitable remotely without authentication, the overall damage potential is constrained by the limited scope of the SSRF in this context. However, organizations in sectors with sensitive internal infrastructure (e.g., finance, healthcare, government) could face increased risk if internal services are accessible via SSRF. Additionally, the public availability of the vulnerability details increases the urgency for European entities to patch promptly to prevent exploitation attempts. The vulnerability could also be leveraged as part of multi-stage attacks, increasing the potential impact beyond the initial SSRF.

Summary

CVE-2025-8133 is a server-side request forgery (SSRF) vulnerability identified in ChanCMS versions up to 3.1.2, specifically within the getArticle function located in the app/modules/api/service/gather.js file. The vulnerability arises due to improper validation or sanitization of the 'targetUrl' argument, which an attacker can manipulate to coerce the server into making unauthorized HTTP requests to arbitrary internal or external resources. This SSRF flaw can be exploited remotely without requiring user interaction or authentication, increasing its risk profile. The vulnerability has been publicly disclosed, and a patch has been released in ChanCMS version 3.1.3 (patch ID 3ef58a50e8b3c427b03c8cf3c9e19a79aa809be6) to remediate the issue. The CVSS v4.0 base score is 5.3 (medium severity), reflecting network attack vector, low attack complexity, no privileges or user interaction required, but limited impact on confidentiality, integrity, and availability. While no known exploits are currently observed in the wild, the public disclosure means threat actors could develop exploits. SSRF vulnerabilities can be leveraged to access internal services, bypass firewalls, or perform reconnaissance, potentially leading to further compromise depending on the internal network's configuration and the server's privileges.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Aug 2025, 01:02 UTC

Technical details

References

Community reviews

Related threats