CVE-2026-0592
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 flaw has been discovered in code-projects Online Product Reservation System 1.0. This affects an unknown function of the file /handgunner-administrator/register_code.php of the component User Registration Handler. Performing a manipulation of the argument fname/lname/address/city/province/country/zip/tel_no/email/username results in sql injection. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks.
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 User Registration Handler of code-projects Online Product Reservation System 1.0 allows remote attackers to inject malicious SQL queries through multiple user input fields (fname, lname, address, city, province, country, zip, tel_no, email, username) in the file /handgunner-administrator/register_code.php.
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 application installationLocate the Online Product Reservation System installation by searching for register_code.php or the application's web root directory. Common paths may include /handgunner-administrator/ or similar admin directories.Affected if The application Fabian Online Product Reservation System version 1.0 is installed on the server.
-
Verify vulnerable file presenceCheck for the existence of the file /handgunner-administrator/register_code.php in the web root. If this file exists, the SQL injection vulnerability may be present.Affected if The file register_code.php exists in the /handgunner-administrator/ directory.
-
Confirm version is 1.0Identify the installed version of the Fabian Online Product Reservation System. Check any version files, about pages, or metadata within the application for the exact version number.Affected if The installed version is exactly 1.0.
-
Verify registration endpoint is accessibleTest if the registration handler is reachable by attempting to access the registration page or submitting a request to /handgunner-administrator/register_code.php.Affected if The registration endpoint is exposed and accessible over the network.
-
Inspect registration code for SQL injection vulnerabilityReview the source code of register_code.php to confirm that user input fields (fname, lname, address, city, province, country, zip, tel_no, email, username) are used directly in SQL queries without parameterized queries or prepared statements.Affected if The code uses direct string concatenation for SQL queries with user inputs without proper sanitization or prepared statements.
A server is affected if it runs Fabian Online Product Reservation System version 1.0 with the accessible file /handgunner-administrator/register_code.php that contains unsanitized SQL queries using user input fields.
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 parameterized queries (prepared statements) for all user inputs in the registration handler, apply strict input validation, and ensure the database user follows least privilege principles.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0592 — 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-0592 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