CVE-2026-0579
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 found in code-projects Online Product Reservation System 1.0. This affects an unknown part of the file /handgunner-administrator/edit.php of the component POST Parameter Handler. The manipulation of the argument prod_id/name/price/model/serial results in sql injection. The attack can be launched 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 confidenceSQL injection vulnerability in the POST parameter handler for /handgunner-administrator/edit.php allows remote attackers to inject malicious SQL queries via the prod_id, name, price, model, or serial parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Fabian Online Product Reservation System installationSearch the web root directory for files containing 'Fabian' or 'Product Reservation System' branding. Check for typical installation paths like /fabian/, /prs/, or /handgunner-administrator/.Affected if The system is present and publicly accessible.
-
Identify the installed versionCheck version.php, README, or CHANGELOG files in the application root for version number. Also check meta tags or footer in the web interface for version information.Affected if Version is 1.0 exactly.
-
Locate the vulnerable scriptNavigate to the web root and search for edit.php within a handgunner-administrator subdirectory. The path should be /handgunner-administrator/edit.php or similar.Affected if The file edit.php exists in the handgunner-administrator directory.
-
Verify POST parameter handling existsExamine the edit.php source code and look for handling of POST parameters: prod_id, name, price, model, or serial. Use grep or a code editor to search for $_POST['prod_id'], $_POST['name'], etc.Affected if The script accepts and processes any of these five POST parameters.
-
Check for SQL query constructionReview edit.php for direct SQL query construction using the POST parameters. Search for patterns like mysql_query, mysqli_query, or PDO exec without parameterized binding. Look for concatenated or interpolated POST values into SQL strings.Affected if The POST parameters are used directly in SQL queries without prepared statements or input sanitization.
If Fabian Online Product Reservation System version 1.0 is installed with edit.php accessible in handgunner-administrator and the POST parameters (prod_id, name, price, model, serial) are processed without parameterized queries, the environment is affected by this SQL injection vulnerability.
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 dataImplement prepared statements/parameterized queries or apply proper input validation and escaping for all POST parameters in edit.php to prevent SQL injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0579 — 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-0579 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