dbcve.org
Web Based Internet Laboratory Management SystemApplication · Itsourcecode

CVE-2025-13300

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability has been found in itsourcecode Web-Based Internet Laboratory Management System 1.0. Affected is an unknown function of the file /settings/controller.php. The manipulation leads to sql injection. It is possible to initiate the attack 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 · high confidence

A SQL injection vulnerability exists in itsourcecode Web-Based Internet Laboratory Management System 1.0 within the /settings/controller.php file. The vulnerability is remotely exploitable and allows attackers to manipulate SQL queries through unsanitized input, potentially enabling data exfiltration or complete database compromise.

MitigationImplement prepared statements or parameterized queries in /settings/controller.php to neutralize SQL injection vectors. Restrict network access to the application until the patch is applied.

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
Web Based Internet Laboratory Management SystemApplication
Affected:= 1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the application installation
    Locate the itsourcecode Web-Based Internet Laboratory Management System installation directory on the server. Look for typical web application paths such as /var/www/html, /www, or C:\inetpub\wwwroot depending on your operating system and web server configuration.
    Affected if The application is installed and running on the system.
  2. Verify the vulnerable file exists
    Inspect the /settings/controller.php file within the application root directory. Check if this file is present and readable.
    Affected if The file /settings/controller.php exists in the application directory.
  3. Confirm the application version
    Check the application version by examining version files, about pages, or the source code headers. Typical locations include a /includes, /config, or root directory files like version.php, about.php, or README files.
    Affected if The installed version is exactly 1.0.
  4. Assess network exposure
    Determine if the web application is accessible over the network by checking your web server configuration, firewall rules, and whether the application is bound to external network interfaces (0.0.0.0) rather than localhost (127.0.0.1).
    Affected if The application is accessible from external network addresses, not just localhost.
  5. Review database configuration
    Examine the database configuration files in the application to identify the database user privileges and connection method used. Look for config.php, db.php, or similar files in the /includes or /config directories.
    Affected if The application uses a database user with elevated privileges (such as root or admin-level) rather than a restricted application-specific user.

You are affected if the itsourcecode Web-Based Internet Laboratory Management System version 1.0 is installed, the /settings/controller.php file exists, and the application is accessible over a network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements or parameterized queries in /settings/controller.php to neutralize SQL injection vectors. Restrict network access to the application until the patch is applied.

Fix this in Web Based Internet Laboratory Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13300 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13300 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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