CVE-2024-0304VulnerabilityPublished 8 Jan 2024Updated 3 Jun 2025

CVE-2024-0304: Youke365 · Server-Side Request Forgery

Affects Youke365Source CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: 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 impacted component.
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 8 Jan 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 2026-10-26.

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
GitHubYouke365`pkg:github/Youke365`Other threats	Affected =1.5.0 =1.5.1 =1.5.2 =1.5.3	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. Immediate mitigation should include restricting access to the vulnerable endpoint (/app/api/controller/collect.php) via network-level controls such as web application firewalls (WAFs) or IP whitelisting to limit exposure. 2. Implement strict input validation and sanitization on the 'url' parameter to ensure only allowed, safe URLs can be processed, ideally using a whitelist approach. 3. Employ network segmentation and firewall rules to prevent the application server from making arbitrary outbound requests to internal resources. 4. Monitor logs for unusual outbound requests originating from the application server to detect potential exploitation attempts. 5. If possible, upgrade or patch Youke365 to a version that addresses this vulnerability once available. 6. Conduct a thorough security review of all components interacting with Youke365 to identify and remediate any chained vulnerabilities. 7. Educate administrators and developers about SSRF risks and secure coding practices to prevent similar issues in the future.

Description

A vulnerability has been found in Youke365 up to 1.5.3 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /app/api/controller/collect.php. The manipulation of the argument url leads to server-side request forgery. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-249871.

Impact

For European organizations using Youke365 versions 1.5.0 through 1.5.3, this SSRF vulnerability poses a significant risk. Exploitation could allow attackers to access internal services that are otherwise inaccessible from the internet, potentially leading to unauthorized data access, internal network mapping, or pivoting to more critical systems. Confidentiality could be compromised if sensitive internal endpoints are exposed. Integrity and availability impacts are also possible if attackers leverage SSRF to trigger unintended actions or denial-of-service conditions on internal services. Given that Youke365 is a web-based application, organizations relying on it for business-critical operations could face operational disruptions. The medium CVSS score reflects that exploitation requires some privileges, which may limit the attack surface but does not eliminate risk, especially in environments with weak access controls. European organizations with sensitive internal networks or regulatory requirements (e.g., GDPR) must consider the potential compliance and reputational impacts of such a vulnerability.

Summary

CVE-2024-0304 is a server-side request forgery (SSRF) vulnerability identified in Youke365 versions up to 1.5.3, specifically within the /app/api/controller/collect.php file. The vulnerability arises from improper validation or sanitization of the 'url' argument, allowing an attacker to manipulate this parameter to make the server perform unintended HTTP requests. SSRF vulnerabilities enable attackers to coerce the vulnerable server into initiating requests to internal or external systems, potentially bypassing firewall restrictions or accessing sensitive internal resources. In this case, the vulnerability can be exploited remotely without user interaction but requires some level of privileges (as indicated by the CVSS vector's PR:L). The CVSS 3.1 base score is 6.3 (medium severity), reflecting that the vulnerability impacts confidentiality, integrity, and availability to a limited extent. Although no public exploits are currently known in the wild, the vulnerability has been disclosed publicly, increasing the risk of exploitation. The lack of available patches or vendor advisories at the time of publication suggests that affected organizations must implement mitigations proactively. The CWE-918 classification confirms the SSRF nature of the flaw, which is a common vector for lateral movement, data exfiltration, and internal network reconnaissance in targeted attacks.

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 3 Jul 2025, 23:58 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats