CVE-2025-0402
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 classified as critical was found in 1902756969 reggie 1.0. Affected by this vulnerability is the function upload of the file src/main/java/com/itheima/reggie/controller/CommonController.java. The manipulation of the argument file leads to unrestricted upload. The attack can be launched 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 · high confidenceUnrestricted file upload vulnerability in the upload function of CommonController.java in reggie 1.0. The application fails to validate file types, extensions, or content before saving uploaded files, allowing attackers to upload malicious executables (web shells, malware) that could lead to remote code execution.
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= 1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if reggie version 1.0 is deployedCheck your application's version identifier, typically found in build files (pom.xml, package.json), WAR file metadata, or the application startup banner/logs. Look for version '1.0' or build identifier '1902756969'.Affected if The installed version is reggie 1.0 (build 1902756969)
-
Locate the CommonController upload endpointSearch your deployed application codebase for CommonController.java or inspect your web application's routing/configuration to find the file upload endpoint. Common paths include /api/upload, /common/upload, or similar paths under the application's controller package.Affected if CommonController.java with an upload function exists in the deployed application
-
Verify file type validation is disabled or missingExamine the source code of the upload handler in CommonController.java. Look for any file type, extension, or MIME type validation logic. Check if there are allowlist or denylist checks before file saving.Affected if No file type, extension, or content-type validation exists before file save operations
-
Test unrestricted file upload capabilityUsing a tool like curl or Burp Suite, send a POST request to the upload endpoint with a malicious file (such as a JSP shell or executable) without any extension or with a double extension (.jpg.php). Observe if the file is accepted and stored.Affected if The application accepts and stores files with any extension or MIME type without validation
-
Check uploaded file storage locationIdentify where uploaded files are stored by reviewing the upload handler code or by uploading a test file and checking the application's file system. Determine if the storage directory is within the webroot and allows script execution.Affected if Uploaded files are stored in a web-accessible directory with script execution enabled
You are affected if you are running reggie version 1.0 and the application accepts and stores uploaded files without validating their type, extension, or content, particularly if files are stored within the webroot.
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 allowlist-based file validation (extension + MIME type + magic bytes), rename uploaded files to random names, store uploads outside webroot, and disable script execution in the upload directory.
- 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-0402 — 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-0402 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