CVE-2025-11347
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 code-projects Student Crud Operation up to 3.3. This vulnerability affects the function move_uploaded_file of the file add.php of the component Add Student Page/Edit Student Page. Performing manipulation results in unrestricted upload. The attack can be initiated remotely. The exploit has been made public and could 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 confidenceAn unrestricted file upload vulnerability exists in the add.php file of the Student Crud Operation application (versions up to 3.3). The move_uploaded_file function lacks proper validation, allowing attackers to upload malicious files (e.g., web shells) to the server remotely, potentially achieving 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<= 3.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Code Projects Crud Operation System is installedSearch for files named add.php, edit.php, or common student management PHP files in the web document root. Look for directories containing 'crud', 'student', or 'code-projects' in the path.Affected if The application is found on the system
-
Determine the installed versionCheck version.php, README.txt, or any version file in the application root. Also check comments in PHP files for version indicators like 'version 3.3' or lower.Affected if Version is 3.3 or lower, or version cannot be determined but the application is present
-
Locate the add.php upload handlerFind add.php in the application directory structure. Common paths may include /student/, /crud/, or at the root of the application.Affected if add.php file exists in the application
-
Verify file upload functionality is enabledInspect add.php for presence of move_uploaded_file function calls. Check if the form has file input fields (type='file') for student data uploads.Affected if move_uploaded_file is used and file upload forms exist in add.php
-
Check for missing file validation in upload logicExamine the PHP code in add.php around move_uploaded_file for validation routines. Look for file extension checks, MIME type validation, or content-type verification.Affected if move_uploaded_file is called without proper validation (no extension allowlist, no MIME type check, no content verification)
-
Confirm uploads are stored in web-accessible locationIdentify the destination path in the move_uploaded_file call. Check if the upload directory is within the web root (htdocs, www, public_html).Affected if Uploads are saved to a directory accessible via HTTP/HTTPS
The environment is affected if Code Projects Crud Operation System version 3.3 or lower is installed with add.php present and file upload functionality enabled without proper validation.
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 upload validation: whitelist allowed file types/extensions, validate MIME type and file content, rename uploaded files, store uploads outside the web root, and disable script execution in the upload directory.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11347 — 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-11347 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