CVE-2025-13301
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 itsourcecode Web-Based Internet Laboratory Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /subject/controller.php. The manipulation results in sql injection. It is possible to launch the attack 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 · moderate confidenceSQL injection vulnerability in /subject/controller.php of itsourcecode Web-Based Internet Laboratory Management System 1.0 allows remote attackers to manipulate database queries. The CVSS 9.8 indicates full compromise of confidentiality, integrity, and availability is possible.
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.
-
Confirm Web-Based Internet Laboratory Management System is installedSearch the web server for files or directories containing 'Internet Laboratory Management System' or check application startup pages for the product nameAffected if The itsourcecode Web-Based Internet Laboratory Management System is found on the server
-
Identify installed versionCheck application configuration files, about pages, or version metadata files for version number 1.0Affected if The installed version is exactly 1.0
-
Locate vulnerable fileCheck for the presence of /subject/controller.php in the web application root directoryAffected if The file /subject/controller.php exists in the application
-
Verify SQL injection vulnerability exists in controller.phpReview the source code of /subject/controller.php for dynamic SQL queries that incorporate user input without parameterizationAffected if User-supplied parameters are directly concatenated into SQL queries within controller.php
-
Confirm remote access exposureVerify the /subject/controller.php endpoint is accessible over the network via HTTP/HTTPS without authenticationAffected if The vulnerable endpoint is reachable from remote network locations
You are affected if you are running version 1.0 of the Itsourcecode Web-Based Internet Laboratory Management System with the /subject/controller.php file exposed and containing unprotected SQL query handling.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements in controller.php, validate and sanitize all user inputs, and apply vendor patch when available. Consider WAF deployment as interim protection.
- 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-13301 — 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-13301 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