CVE-2025-10781
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 Campcodes Online Learning Management System 1.0. This impacts an unknown function of the file /admin/edit_class.php. Such manipulation of the argument class_name leads to sql injection. The attack can be executed remotely. 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 · moderate confidenceSQL injection vulnerability in Campcodes Online Learning Management System 1.0 allows remote attackers to inject arbitrary SQL commands through the class_name parameter in /admin/edit_class.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries.
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 versionLocate any version identifier in the application (e.g., in admin panel footer, about page, or version file). Compare against the affected version: 1.0Affected if The application version is exactly 1.0 of Campcodes Online Learning Management System
-
Verify the vulnerable script existsCheck if the file /admin/edit_class.php exists in the web root directoryAffected if The file /admin/edit_class.php is present in the installation
-
Confirm admin interface is accessibleAttempt to access the /admin/ path or check if admin authentication is enabled and reachableAffected if The admin panel is accessible (either unauthenticated or with valid admin credentials)
-
Inspect the edit_class.php source codeOpen /admin/edit_class.php and examine how the class_name parameter is handled in database queries. Look for direct insertion into SQL statements without sanitization functions or prepared statementsAffected if The code contains SQL queries using the class_name parameter without using parameterized queries, prepared statements, or input sanitization functions
-
Check web server logs for exploitation attemptsReview web server access logs for requests to /admin/edit_class.php containing SQL injection payloads in the class_name parameterAffected if Suspicious SQL injection patterns are found in logs for this endpoint
A user is affected if they are running Campcodes Online Learning Management System version 1.0, the /admin/edit_class.php file exists, the admin interface is accessible, and the class_name parameter is handled without parameterized queries or input sanitization.
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 prepared statements and implement proper input validation for the class_name parameter. Apply vendor patches if available and conduct a broader code review for similar SQL injection vulnerabilities.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10781 — 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-10781 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