dbcve.org
InjectionWeakness · CWE-74

CVE-2026-8128

HIGH · 7.3 CVSS v3.1 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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 SourceCodester SUP Online Shopping 1.0. The affected element is an unknown function of the file /admin/viewmsg.php. Performing a manipulation of the argument msgid 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 · moderate confidence

SQL injection vulnerability in /admin/viewmsg.php via the msgid parameter allows remote attackers to inject malicious SQL queries.

MitigationImplement prepared statements/parameterized queries for the msgid parameter in viewmsg.php and add input validation.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the vulnerable PHP file
    Search for the file /admin/viewmsg.php in the web root directory of the application
    Affected if The file exists in the application installation
  2. Verify the msgid parameter is handled
    Inspect the viewmsg.php file and search for usage of the $_GET['msgid'] or $_POST['msgid'] parameter in the code
    Affected if The msgid parameter is directly used without sanitization
  3. Confirm lack of prepared statements
    Search the viewmsg.php file for SQL query patterns involving msgid - look for direct string concatenation or interpolation instead of parameterized queries
    Affected if SQL queries involving msgid are constructed without prepared statements or parameterized queries
  4. Check for input validation
    Search the viewmsg.php file for validation functions (e.g., intval, filter_var, preg_match) applied to the msgid parameter before SQL use
    Affected if No input validation is performed on the msgid parameter before it is used in SQL queries
  5. Review database query logs
    If accessible, examine database logs or web application firewall logs for unusual SQL syntax in msgid-related queries
    Affected if Unexpected SQL syntax or UNION SELECT patterns appear in msgid parameter values in logs

The environment is affected if the /admin/viewmsg.php file exists and processes the msgid parameter directly in SQL queries without prepared statements, parameter binding, or input validation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for the msgid parameter in viewmsg.php and add input validation.

Recommended fix Moderate confidence

Check SourceCodester for any newer version of SUP Online Shopping that addresses this SQL injection vulnerability

  1. 1. Locate the file /admin/viewmsg.php in the SourceCodester SUP Online Shopping 1.0 application
  2. 2. Identify the SQL query that uses the 'msgid' parameter unsafely
  3. 3. Replace the vulnerable query with a parameterized query (prepared statement) using PDO or mysqli
  4. 4. Example fix: Change from `SELECT * FROM messages WHERE msgid='$msgid'` to using prepared statements like `$stmt = $pdo->prepare('SELECT * FROM messages WHERE msgid = :msgid'); $stmt->execute(['msgid' => $msgid]);`
  5. 5. Alternatively, use mysqli: `$stmt = $mysqli->prepare('SELECT * FROM messages WHERE msgid = ?'); $stmt->bind_param('i', $msgid);`
  6. 6. Test the fix by attempting SQL injection via the msgid parameter to confirm it is mitigated
  7. 7. Deploy the fixed file to the production environment

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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