CVE-2024-13133
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, which was classified as critical, has been found in ZeroWdd studentmanager 1.0. This issue affects the function addStudent/editStudent of the file src/main/Java/com/wdd/studentmanager/controller/StudentController. java. The manipulation of the argument file leads to unrestricted upload. The attack may 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 ZeroWdd studentmanager 1.0's StudentController.java (addStudent/editStudent functions). Remote attackers can upload arbitrary files by manipulating the 'file' argument, potentially achieving remote code execution via web shells or malicious executables.
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 ZeroWdd Studentmanager 1.0 is installedCheck for the application by looking for studentmanager or related webapp directories, or by probing for typical paths like /studentmanager, /students, or the application's WAR/JAR files in the web server's webapps directoryAffected if The application is running and accessible on the system
-
Verify the StudentController.java upload endpoint existsCheck the application's deployment for StudentController.class or the source file StudentController.java, specifically looking for addStudent and editStudent functions that handle the 'file' parameterAffected if The StudentController with upload functionality is present in the deployed application
-
Test if file upload accepts arbitrary extensionsAttempt to access the student add/edit forms and submit a request with a non-image file (such as .jsp, .php, .exe, or .html) to the 'file' parameter using a web proxy or curlAffected if The application accepts and stores files with dangerous extensions without validation
-
Check if uploaded files are served from webrootInspect the application's configuration to determine if uploaded files are stored in a directory accessible via web browser (within webapps or htdocs)Affected if Uploaded files are stored in a web-accessible directory and can be executed via HTTP requests
-
Verify if file type validation is implementedReview the StudentController.java or any filter/interceptor configuration to check if extension allowlisting or magic-byte validation is performed on uploadsAffected if No extension allowlisting or content-type validation is found in the upload handling code
The environment is affected if ZeroWdd Studentmanager 1.0 is deployed with the StudentController upload functionality accessible and without proper file type validation on the 'file' parameter.
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 type validation using both extension and magic-byte verification, store uploads outside the webroot with no execute permissions, and add content-type headers to prevent direct script execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13133 — 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-13133 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