CVE-2026-8129
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 determined in SourceCodester SUP Online Shopping 1.0. The impacted element is an unknown function of the file wishlist.php. Executing a manipulation of the argument delwlistid can lead to sql injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized.
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 SourceCodester SUP Online Shopping 1.0's wishlist.php file. The 'delwlistid' parameter passed to an unspecified function is not properly sanitized, allowing attackers to inject malicious SQL queries. This can lead to unauthorized database access, data exfiltration, or potential remote code execution depending on database configuration.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed applicationLocate and confirm the presence of SourceCodester SUP Online Shopping application on the system. Check web root directories for files named 'wishlist.php' or look for the SUP Online Shopping codebase.Affected if The application is SourceCodester SUP Online Shopping version 1.0 or earlier and contains a wishlist.php file
-
Confirm the application versionCheck the application version number through any version file, footer text, or metadata within the SUP Online Shopping installation. Compare against the affected version (1.0).Affected if The installed version is SUP Online Shopping 1.0 or earlier
-
Verify wishlist.php exists and is accessibleCheck for the presence of wishlist.php file in the web-accessible directories of the application. This file should exist in the application structure.Affected if wishlist.php file exists in the application web directory
-
Inspect the delwlistid parameter handling in wishlist.phpOpen wishlist.php and examine how the 'delwlistid' parameter is processed. Look for direct use of this parameter in SQL queries without proper sanitization, parameterization, or prepared statements.Affected if The delwlistid parameter is used in SQL queries without sanitization, parameter binding, or prepared statements
-
Determine if wishlist delete functionality is enabledCheck if the wishlist feature and its delete functionality (linked to delwlistid parameter) is accessible to users, either authenticated or unauthenticated, through HTTP requests.Affected if The wishlist delete functionality using delwlistid parameter is accessible via HTTP and the code contains unsanitized SQL query construction
A user is affected if they have SourceCodester SUP Online Shopping version 1.0 or earlier with wishlist.php present and the delwlistid parameter handled without parameterized queries in the code.
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/prepared statements for the delwlistid parameter in wishlist.php. Implement strict input validation and apply principle of least privilege to the database user. Consider deploying a WAF as a temporary compensating control while the code fix is being developed.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8129 — 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-8129 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