CVE-2026-4876
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 identified in itsourcecode Free Hotel Reservation System 1.0. The impacted element is an unknown function of the file /admin/mod_amenities/index.php?view=editpic. Such manipulation of the argument ID leads to sql injection. The attack may be performed from remote. The exploit is publicly available and might 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 itsourcecode Free Hotel Reservation System 1.0 allows remote attackers to inject malicious SQL queries via the 'ID' parameter in the /admin/mod_amenities/index.php?view=editpic endpoint. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 if itsourcecode Free Hotel Reservation System is installedLocate the web application files on the server - typically found in the web root directory (e.g., htdocs, www, public_html). Look for the 'Free Hotel Reservation System' application structure, particularly the /admin/mod_amenities/ directory.Affected if The application files for Free Hotel Reservation System exist on the server
-
Verify the application version is 1.0Check for version information in the application - look for a version file, about page, or check the source code for version indicators. Common locations include a VERSION file, README, or the main index.php header comments.Affected if The installed version is Free Hotel Reservation System 1.0
-
Confirm the vulnerable endpoint existsCheck if the file /admin/mod_amenities/index.php exists in the application installation directory. This file handles the editpic functionality when the 'view' parameter is set to 'editpic'.Affected if The file admin/mod_amenities/index.php exists and accepts the 'view' parameter
-
Inspect the source code for the ID parameter handlingOpen /admin/mod_amenities/index.php and locate the code that handles the 'ID' parameter when 'view=editpic'. Examine whether the ID value is directly concatenated into SQL queries without using prepared statements or parameterized queries.Affected if The ID parameter is used directly in SQL queries without prepared statements, input sanitization, or escaping functions (such as mysqli_prepare, PDO::prepare, or escaping functions like mysqli_real_escape_string)
The environment is affected if Free Hotel Reservation System version 1.0 is installed, the admin/mod_amenities/index.php file exists, and the ID parameter in the editpic functionality is processed without parameterized queries or proper input sanitization.
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 or parameterized queries for the ID parameter in the editpic functionality. Apply input validation and escaping for all user-supplied parameters before constructing database queries.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4876 — 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-4876 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