CVE-2026-5580
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 CodeAstro Online Classroom 1.0. Impacted is an unknown function of the file /OnlineClassroom/addvideos.php of the component Parameter Handler. The manipulation of the argument videotitle leads to sql injection. It is possible to initiate the attack 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 · high confidenceSQL injection vulnerability in CodeAstro Online Classroom 1.0's addvideos.php file. The videotitle parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 CodeAstro Online Classroom installationSearch the web root directory for files named 'addvideos.php' or directories containing 'OnlineClassroom'. Common paths: /var/www/html/OnlineClassroom/ or C:\xampp\htdocs\OnlineClassroom\Affected if The application files are found on the server in a web-accessible directory
-
Identify installed versionCheck for a version file, README, or any file containing version metadata within the OnlineClassroom installation directory. Also check footer files or admin panels for version strings.Affected if The installed version is 1.0 or cannot be determined (treat as potentially affected)
-
Verify vulnerable script existsLocate the file /OnlineClassroom/addvideos.php in the web root. Verify the file exists and contains database query logic using the 'videotitle' parameter.Affected if The file addvideos.php exists and processes the videotitle parameter in SQL queries without visible sanitization
-
Check remote accessibilityDetermine if the application is accessible from untrusted networks. Test accessing the addvideos.php endpoint via HTTP from an external IP or the internet.Affected if The application endpoint is reachable remotely without VPN or firewall restrictions
-
Verify lack of authentication on vulnerable endpointAttempt to access /OnlineClassroom/addvideos.php directly without logging in. Check if the page loads or accepts requests without session credentials.Affected if The addvideos.php endpoint is accessible without authentication
A defender is affected if CodeAstro Online Classroom 1.0 is installed, the addvideos.php file exists with the videotitle parameter handling, and the endpoint is accessible remotely or without authentication.
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 or prepared statements. Implement input validation and escaping for all user-supplied parameters before database operations.
- 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-2026-5580 — 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-2026-5580 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