CVE-2025-2671
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 · uneditedA vulnerability was found in Yue Lao Blind Box 月老盲盒 up to 4.0. It has been declared as critical. This vulnerability affects the function base64image of the file /app/controller/Upload.php. The manipulation of the argument data leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
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 · moderate confidenceUnrestricted file upload vulnerability in the base64image function of /app/controller/Upload.php in Yue Lao Blind Box up to v4.0. Attackers can manipulate the base64-encoded data argument to upload arbitrary files (including executable scripts) to the server, potentially achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the application and versionLocate the application version file or header - common paths include version.php, about.php, or check the admin dashboard for version information. Compare the installed version to v4.0.Affected if The application is Yue Lao Blind Box version 4.0 or lower.
-
Verify the vulnerable file existsCheck if /app/controller/Upload.php exists in the webroot or application directory.Affected if The file /app/controller/Upload.php exists in the application.
-
Confirm the base64image function is presentOpen /app/controller/Upload.php and search for the string 'function base64image' or 'base64image' to verify the vulnerable function exists.Affected if The base64image function is defined in Upload.php.
-
Check upload directory accessibilityExamine the application configuration or code to determine where uploaded files are stored. Verify if the upload directory is within the webroot and accessible via HTTP.Affected if Uploaded files are stored in a web-accessible directory.
-
Test if upload functionality is exposedAttempt to access the upload endpoint directly - typically through the base64image function via POST request with a base64-encoded payload. Check if authentication is required.Affected if The upload functionality is accessible without authentication or with weak authentication.
You are affected if you are running Yue Lao Blind Box v4.0 or lower, the file /app/controller/Upload.php with the base64image function exists, and the upload functionality is accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement strict server-side file type validation by checking magic bytes/content-type, enforce allowed extensions whitelist, store uploads outside webroot with no script execution permissions, and add filename sanitization.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2671 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2671 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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