dbcve.org
InjectionWeakness · CWE-74

CVE-2026-5578

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 was found in CodeAstro Online Classroom 1.0. This vulnerability affects unknown code of the file /OnlineClassroom/addassessment.php of the component Parameter Handler. Performing a manipulation of the argument deleteid results in sql injection. The attack is possible to be carried out remotely. The exploit has been made public and could 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

SQL injection vulnerability in CodeAstro Online Classroom 1.0's /OnlineClassroom/addassessment.php via the deleteid parameter, allowing remote attackers to manipulate SQL queries and potentially extract or modify database contents.

MitigationImplement parameterized queries (prepared statements) for the deleteid parameter in addassessment.php and add proper input validation to prevent SQL injection attacks.

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 checks

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

  1. Confirm CodeAstro Online Classroom installation
    Locate the web root directory and search for files or directories containing 'CodeAstro' or 'OnlineClassroom' in the filename or check the application banner/version information in the web interface.
    Affected if The application CodeAstro Online Classroom is present on the server.
  2. Verify the application version
    Check for version information in source files, README files, or the admin panel of the application. Look for version strings matching '1.0' or similar.
    Affected if The installed version is CodeAstro Online Classroom 1.0.
  3. Check for the vulnerable file
    Locate the file /OnlineClassroom/addassessment.php within the web root. Search for this specific file path and verify it exists.
    Affected if The file addassessment.php exists in the /OnlineClassroom/ directory.
  4. Examine deleteid parameter handling
    Review the source code of addassessment.php to determine if the deleteid parameter is used in SQL queries without prepared statements or parameter binding. Search for SQL query construction involving deleteid.
    Affected if The deleteid parameter is directly concatenated into SQL queries without sanitization or parameterized queries.

A system is affected if CodeAstro Online Classroom 1.0 is installed and the addassessment.php file processes the deleteid parameter without SQL injection protection.

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 parameterized queries (prepared statements) for the deleteid parameter in addassessment.php and add proper input validation to prevent SQL injection attacks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5578 — 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-2026-5578 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