LiveActive security incident?Get immediate response
CVE Record

CVE-2021-31650: A SQL injection vulnerability in Sourcecodester Online Grading System 1.0 allows remote attackers to execut...

A SQL injection vulnerability in Sourcecodester Online Grading System 1.0 allows remote attackers to execute arbitrary SQL commands via the uname parameter.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE is a critical SQL injection issue in Sourcecodester Online Grading System 1.0. A remote, unauthenticated attacker may be able to manipulate database queries through the uname parameter, risking data theft, data modification, or service disruption.

Executive priority

Treat as urgent for any exposed deployment. The issue can affect the core database without login, and public exploit information exists. If the product is not deployed, priority drops to inventory confirmation.

Technical view

CVE-2021-31650 is CWE-89 SQL injection affecting the uname parameter in Sourcecodester Online Grading System 1.0. The CVSS 3.1 score is 9.8, reflecting network access, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to organizations running Sourcecodester Online Grading System 1.0, especially if reachable from the internet. The source bundle does not provide CPEs or broader affected-version data, so asset confirmation is essential.

Exploitation context

A public Exploit-DB reference exists, indicating public technical knowledge. The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation in the wild.

Researcher notes

The affected metadata in the bundle is sparse, listing vendor/product as n/a despite the CVE title and description naming Sourcecodester Online Grading System 1.0. Avoid assuming other versions or forks are affected without local testing or vendor evidence.

Mitigation direction

  • Check Sourcecodester or project maintainer guidance for a fixed release or advisory.
  • If no supported fix exists, retire, replace, or isolate affected deployments.
  • Restrict public access to the grading system until remediation is confirmed.
  • Review uname handling for parameterized database queries before restoring exposure.

Validation and detection

  • Inventory deployments of Sourcecodester Online Grading System and confirm version 1.0 exposure.
  • Review authentication or login code paths that process the uname parameter.
  • Check application and database logs for SQL errors or suspicious uname input.
  • Confirm whether any affected instance is internet-accessible.
  • Verify compensating access controls are active until a fix is confirmed.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-31650 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2021-31650Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.