dbcve.org
InjectionWeakness · CWE-74

CVE-2026-6142

HIGH · 7.3 CVSS v3.1 Published 2026-04-13
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 identified in tushar-2223 Hotel Management System up to bb1f3b3666124b888f1e4bcf51b6fba9fbb01d15. Affected by this vulnerability is an unknown functionality of the file /admin/roomdelete.php. The manipulation of the argument ID leads to sql injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The project was informed of the problem early through an issue report but has not responded yet.

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 confidence

SQL injection vulnerability in /admin/roomdelete.php allows remote attackers to inject malicious SQL queries via the ID parameter. The vulnerability is exploitable without authentication and a public exploit exists.

MitigationImplement prepared statements/parameterized queries for all database operations in roomdelete.php, or apply input validation and sanitization as an interim measure until the vendor releases a patch.

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
    Check if /admin/roomdelete.php exists in your web application's document root or admin directory
    Affected if The file exists in the expected location on the server
  2. Verify the ID parameter handling
    Examine the source code of roomdelete.php and look for SQL queries that incorporate the ID parameter without using prepared statements or parameter binding
    Affected if The code constructs SQL queries by directly concatenating or interpolating the ID parameter into the query string
  3. Confirm unauthenticated access
    Attempt to access /admin/roomdelete.php without providing any authentication credentials (cookies, session tokens, or Basic Auth)
    Affected if The endpoint responds without requiring authentication or returns a 200 OK status instead of redirecting to a login page
  4. Test for SQL injection susceptibility
    Send a crafted request to /admin/roomdelete.php with a test payload in the ID parameter (for example: ID=1' OR '1'='1) and observe the application response or database error messages
    Affected if The application returns database errors, unexpected data, or behaves differently based on the payload (true/false conditions)
  5. Check application version against vendor advisories
    Identify the installed application version from version files, headers, or the application itself, then compare against any vendor-released patched versions or security advisories
    Affected if The installed version has not yet received a patch for this CVE or the vendor has not released a security update addressing this issue

Your environment is affected if the roomdelete.php file exists, handles the ID parameter without prepared statements, is accessible without authentication, and runs an unpatched version of the software.

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 all database operations in roomdelete.php, or apply input validation and sanitization as an interim measure until the vendor releases a patch.

Recommended fix High confidence
  1. 1. Locate the vulnerable file /admin/roomdelete.php in the application codebase
  2. 2. Identify the SQL query that uses the 'ID' parameter without proper sanitization
  3. 3. Use prepared statements (PDO prepared statements or mysqli_prepare) to replace dynamic SQL concatenation with parameterized queries
  4. 4. Validate and sanitize the 'ID' input - ensure it contains only expected characters (e.g., numeric values for room IDs)
  5. 5. Apply input validation: use intval() or type casting to ensure ID is an integer before using in queries
  6. 6. Implement least-privilege database credentials - ensure the database user for this application has only necessary permissions
  7. 7. Test the patched file to confirm the SQL injection is mitigated
  8. 8. Deploy the patched file to production environment
Caveat No upgrade path available - vendor has not released a fix; rolling release model with no patched version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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