CVE-2025-11077
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 determined in Campcodes Online Learning Management System 1.0. Affected is an unknown function of the file /admin/add_content.php. Executing manipulation of the argument Title can lead to sql injection. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized.
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 malicious SQL queries via the Title parameter in /admin/add_content.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially allowing unauthorized data access, modification, or complete system compromise.
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 Campcodes LMS installationLocate the web application's root directory. Look for files or directories typical of Campcodes Online Learning Management System, such as login pages, admin panels, or characteristic filenames.Affected if The application is Campcodes Online Learning Management System and version 1.0 is installed.
-
Verify the affected file existsCheck if /admin/add_content.php exists in the web root directory. Access the file via a web browser or verify its presence in the file system.Affected if The file /admin/add_content.php exists in the application.
-
Identify the Title parameter handlingOpen /admin/add_content.php and search for the code handling the 'Title' POST or GET parameter. Look for database query execution (SELECT, INSERT, UPDATE) involving this parameter.Affected if The Title parameter is used in SQL queries without visible sanitization or prepared statement usage.
-
Inspect for input sanitizationExamine the PHP code around the Title parameter for functions like mysqli_real_escape_string, htmlspecialchars, preg_replace, or any validation logic before the SQL query execution.Affected if No input sanitization or validation is performed on the Title parameter before it is used in SQL queries.
-
Confirm lack of prepared statementsSearch the add_content.php file for prepare(), bind_param(), or similar prepared statement method calls. Check if the SQL query uses parameter binding.Affected if The database queries involving the Title parameter are executed without prepared statements or parameter binding.
A user is affected if they run Campcodes Online Learning Management System version 1.0 with the /admin/add_content.php file accessible and the Title parameter processed without sanitization or 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 dataImplement prepared statements/parameterized queries for all database operations and apply proper input validation on the Title parameter. Restrict admin panel access to authorized users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11077 — 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-11077 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