CVE-2025-11064
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 security flaw has been discovered in Campcodes Online Learning Management System 1.0. Impacted is an unknown function of the file /admin/teachers.php. The manipulation of the argument department results in sql injection. It is possible to launch the attack remotely. The exploit has been released to the public and may be exploited.
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 confidenceSQL injection vulnerability in Campcodes Online Learning Management System 1.0 allows remote attackers to inject malicious SQL queries via the 'department' parameter in /admin/teachers.php. The lack of parameterized queries or input sanitization enables attackers to manipulate database queries, potentially extracting, modifying, or deleting sensitive data, or potentially achieving remote code execution depending on database configuration.
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 the installed product is Campcodes Online Learning Management SystemInspect the application or check the web server's deployed files to identify the product name and version. Look for any version标识或about页面 that displays version 1.0.Affected if The installed version is Campcodes Online Learning Management System version 1.0 exactly.
-
Verify /admin/teachers.php existsLocate the teachers.php file in the /admin/ directory of the web application. This file is where the SQL injection vulnerability resides.Affected if The file /admin/teachers.php exists in the deployed application.
-
Inspect the department parameter handling in teachers.phpOpen teachers.php and examine the code that handles the 'department' parameter. Look for database query code that incorporates the department parameter directly into SQL statements without using prepared statements or parameterization.Affected if The code takes the 'department' parameter and passes it directly into an SQL query without sanitization or parameterized queries.
-
Check if the /admin/ directory is accessible without authenticationAttempt to access the /admin/teachers.php endpoint directly over the network without providing login credentials. This CVE is described as exploitable by unauthenticated attackers.Affected if The /admin/ interface and teachers.php are accessible without authentication.
You are affected if you are running Campcodes Online Learning Management System version 1.0 with the /admin/teachers.php file present and the 'department' parameter is handled in SQL queries without prepared statements.
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 dataImmediate remediation requires rewriting the vulnerable queries in teachers.php to use prepared statements/parameterized queries with proper input validation. Until the patch is deployed, consider restricting access to /admin/teachers.php via network-level controls or deploying a WAF rule to block SQL injection patterns.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.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-11064 — 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-11064 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