CVE-2025-10425
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 identified in 1000projects Online Student Project Report Submission and Evaluation System 1.0. The impacted element is an unknown function of the file /admin/controller/student_controller.php. Such manipulation of the argument new_image leads to unrestricted upload. The attack may be performed from remote. The exploit is publicly available and might 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 confidenceThe Online Student Project Report Submission and Evaluation System 1.0 contains an unrestricted file upload vulnerability in /admin/controller/student_controller.php. The 'new_image' parameter accepts files without proper validation, allowing remote attackers to upload malicious files (such as PHP webshells) to the server. The public availability of the exploit and the critical CVSS score indicate active exploitation is likely.
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
- 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 the application is presentSearch for files or directories matching the Online Student Project Report Submission and Evaluation System, typically installed on a web server. Look for the main entry point or characteristic file paths.Affected if The application is found running on the server
-
Verify the installed versionLocate version information for the installed application. Check common version files, headers, or the application itself for a version string of 1.0.Affected if The installed version is 1.0
-
Confirm the vulnerable file existsCheck for the presence of /admin/controller/student_controller.php in the web application directory structure.Affected if The file student_controller.php exists in the /admin/controller/ directory
-
Assess admin interface exposureDetermine if the /admin/ directory and its controller files are accessible over the network, typically on HTTP/HTTPS ports.Affected if The /admin/ interface is network-accessible without proper access controls
-
Scan for suspicious uploaded filesSearch the web root and upload directories for unexpected PHP files, especially those with names suggesting webshells (e.g., shell.php, cmd.php, aaaa.php) or recently created executable files.Affected if Unknown or suspicious PHP files with executable extensions are found in web-accessible directories
A user is affected if they are running version 1.0 of the Online Student Project Report Submission and Evaluation System with the vulnerable student_controller.php file accessible on their server.
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 file extension and MIME type checks, validate actual file content/headers, store uploads outside webroot or with non-executable extensions, and rename uploaded files to prevent execution.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10425 — 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-10425 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