dbcve.org
Event Management SystemApplication · Admerc

CVE-2026-2689

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 detected in itsourcecode Event Management System 1.0. Affected is an unknown function of the file /admin/manage_booking.php. The manipulation of the argument ID results in sql injection. The attack may be performed from remote. The exploit is now public and may 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 confidence

A SQL injection vulnerability exists in itsourcecode Event Management System 1.0 in the /admin/manage_booking.php file. The 'ID' parameter is not properly sanitized before use in SQL queries, allowing remote attackers to inject malicious SQL statements. This critical flaw (CVSS 9.8) could allow unauthorized database access, data exfiltration, or administrative compromise.

MitigationImmediately implement parameterized queries or prepared statements for all database operations using the ID parameter. Consider deploying a WAF rule as an interim measure and restrict admin panel access until the fix is verified.

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
Event Management SystemApplication
Affected:= 1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Event Management System installation
    Search the web root for files named 'manage_booking.php' or check for directory /admin/ on the web server. Look for application files indicating itsourcecode or Admerc Event Management System version 1.0.
    Affected if The system has manage_booking.php present in an /admin/ directory under a web-facing application path.
  2. Identify the vulnerable code location
    Open manage_booking.php and examine how the ID parameter is processed. Search for SQL query patterns that include the ID parameter without prepared statements or sanitization functions.
    Affected if The file contains SQL queries where $_GET['ID'] or $_POST['ID'] is directly concatenated into the query string without parameterized binding.
  3. Check input handling for the ID parameter
    Review the code around lines where the ID parameter is used in database queries. Look for absence of mysqli_prepare, PDO::prepare, or any escaping/sanitization functions like mysqli_real_escape_string or htmlspecialchars used before SQL execution.
    Affected if The ID parameter is used directly in SQL queries without any escaping, type casting (intval), or prepared statement usage.
  4. Verify admin endpoint accessibility
    Check if the /admin/manage_booking.php endpoint is accessible from the web. Test by accessing the URL directly. If the application requires authentication, note that the vulnerability could still be exploitable if the attacker has any valid admin session or if authentication is flawed.
    Affected if The manage_booking.php file is accessible and processes the ID parameter without requiring authentication that would prevent external requests.

The environment is affected if the Event Management System 1.0 is installed with manage_booking.php present and the ID parameter is used in SQL queries without prepared statements or input sanitization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately implement parameterized queries or prepared statements for all database operations using the ID parameter. Consider deploying a WAF rule as an interim measure and restrict admin panel access until the fix is verified.

Fix this in Event Management System Scoped from the published advisory
  • Consultation5.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA3.0 h
28.0 hours of engineering $4,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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