CVE-2024-12700
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 · uneditedThere is an unrestricted file upload vulnerability where it is possible for an authenticated user (low privileged) to upload an jsp shell and execute code with the privileges of user running the web server.
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 allowing authenticated low-privileged users to upload malicious JSP shells and execute arbitrary code with web server user privileges.
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
- 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 product and versionCheck the web application framework or product installed (e.g., from application banner, configuration files, or software inventory). Compare the installed version against any known affected version ranges provided by the vendor.Affected if The product version falls within the affected range and the vendor has listed this CVE as applicable.
-
Verify file upload functionality existsLocate any file upload endpoints in the application (e.g., /upload, /fileupload, profile picture upload, document upload). Check if the application accepts file uploads through web forms, APIs, or administrative interfaces.Affected if The application has active file upload functionality that accepts files from authenticated users.
-
Confirm JSP file execution is enabledInspect the web server or application configuration to determine if JSP files can be executed in the upload directory. Check web.xml for servlet mappings and directory handler configurations. Verify if uploaded .jsp or .jspx files are treated as executable servlets.Affected if The server is configured to process JSP files and the upload directory is web-accessible with script execution enabled.
-
Review upload authorization for low-privileged usersTest or review the access control configuration to determine if low-privileged or unauthenticated users can access the file upload functionality. Examine role-based access control (RBAC) settings and upload permission policies.Affected if Authenticated users with low privileges (non-admin) can access and use the file upload feature.
Your environment is affected if the product has file upload functionality accessible to low-privileged authenticated users, and the server allows uploaded JSP files to be executed as scripts.
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 file type validation using magic byte analysis, restrict upload directories to prevent script execution, enforce proper authorization checks for upload functionality, and disable JSP execution in upload directories.
- 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-2024-12700 — 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-2024-12700 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