dbcve.org
Youke 365Application · Youke365

CVE-2024-0304

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-08
Fix available
A fix is available. Upgrade to after 1.5.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A Server-Side Request Forgery (SSRF) vulnerability in Youke365 up to v1.5.3 in the /app/api/controller/collect.php endpoint allows remote attackers to manipulate the 'url' parameter to make the server perform arbitrary requests to internal or external resources. With CVSS 9.8 (Critical), this can expose internal services, cloud metadata, or enable port scanning of internal networks.

MitigationImplement strict URL validation/allow-listing for the 'url' parameter in collect.php, restrict network access to sensitive internal resources, and upgrade to a patched version when available. Consider disabling the collect functionality if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Youke 365Application
Affected:>= 1.5.0, <= 1.5.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Youke365 version
    Locate the Youke365 installation and identify its version number (commonly found in a version file, admin panel, or software metadata).
    Affected if The installed version is between 1.5.0 and 1.5.3 inclusive.
  2. Confirm collect.php endpoint exists
    Check if the file /app/api/controller/collect.php exists in the web application root directory.
    Affected if The file exists and is present on the server.
  3. Verify endpoint is web-accessible
    Attempt an HTTP request to the /app/api/controller/collect.php endpoint from an authorized position within your network.
    Affected if The endpoint responds to HTTP requests (returns 200 or other valid response rather than 404).
  4. Check if collect functionality is enabled
    Review application configuration files or settings to determine whether the collect feature/module is actively enabled.
    Affected if The collect functionality is enabled and operational.

Your environment is affected if Youke365 version 1.5.0 through 1.5.3 is installed, the collect.php endpoint exists and is web-accessible, and the collect feature is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.5.3
Interim mitigation

Implement strict URL validation/allow-listing for the 'url' parameter in collect.php, restrict network access to sensitive internal resources, and upgrade to a patched version when available. Consider disabling the collect functionality if not required.

Recommended fix Moderate confidence

Youke 365 version > 1.5.3 (latest stable release)

  1. 1. Back up the current Youke 365 installation and database before making any changes.
  2. 2. Download the latest version of Youke 365 from the official vendor repository or website.
  3. 3. Upgrade Youke 365 to the latest available version (version > 1.5.3).
  4. 4. Verify the upgrade was successful by checking the application version.
  5. 5. Test the /app/api/controller/collect.php functionality to ensure it operates correctly after the upgrade.
  6. 6. If the upgrade is not immediately possible, implement network-level filtering to restrict outgoing requests from the application server, limiting SSRF impact.
  7. 7. Monitor logs for any suspicious outbound requests that may indicate exploitation attempts.
Caveat Review release notes for any breaking changes between 1.5.3 and the target upgrade version before deploying in production.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Youke 365 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0304 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data