CVE-2026-7196
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 vulnerability has been detected in CodeAstro Online Classroom 1.0. Affected is an unknown function of the file /guestdetails. Such manipulation of the argument deleteid leads to sql injection. The attack may be performed from remote. The exploit has been disclosed publicly and may 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 CodeAstro Online Classroom 1.0's /guestdetails endpoint where the deleteid parameter fails to sanitize user input, allowing remote attackers to inject malicious SQL queries via the vulnerable parameter.
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.
-
Identify the installed version of CodeAstro Online ClassroomLocate version information in the application by checking the main page footer, an about page, or version files within the web root directory.Affected if The installed version is CodeAstro Online Classroom 1.0.
-
Verify the /guestdetails endpoint existsAccess the URL path /guestdetails on the web server hosting the application to confirm the endpoint is present and accessible.Affected if The /guestdetails endpoint returns a valid HTTP response (200 or similar).
-
Confirm the deleteid parameter is processed by the endpointSubmit a request to /guestdetails with a deleteid parameter (even with a dummy value) and observe if the application processes it.Affected if The application accepts and processes the deleteid parameter without rejecting it.
-
Check for SQL injection protection on the deleteid parameterReview the source code for the guestdetails functionality to determine if prepared statements or parameterized queries are used for the deleteid parameter.Affected if The application does NOT use prepared statements or parameterized queries for the deleteid parameter, leaving it vulnerable to SQL injection.
-
Verify the guestdetails feature is enabled and accessibleConfirm the guestdetails functionality is not disabled or restricted by configuration settings.Affected if The guestdetails feature is enabled and publicly accessible without authentication requirements.
A user is affected if they are running CodeAstro Online Classroom version 1.0 with the /guestdetails endpoint accessible and the deleteid parameter processed without parameterized queries.
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 for all database operations, particularly the deleteid parameter in /guestdetails. Apply input validation and output encoding as defense-in-depth measures.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7196 — 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-7196 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