dbcve.org
Event Management SystemApplication · Admerc

CVE-2026-2217

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-09
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 found in itsourcecode Event Management System 1.0. The impacted element is an unknown function of the file /admin/manage_user.php. The manipulation of the argument ID results in sql injection. The attack may 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 confidence

SQL injection vulnerability in itsourcecode Event Management System 1.0 allows remote attackers to manipulate the ID parameter in /admin/manage_user.php to inject malicious SQL queries, potentially enabling unauthorized data access, modification, or complete system compromise.

MitigationImplement prepared statements/parameterized queries for all database operations, particularly on the ID parameter in manage_user.php; apply input validation and least-privilege database accounts as defense-in-depth measures.

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. Identify if Event Management System is installed
    Check your web server document root for itsourcecode or Admerc Event Management System files. Look for directories named 'event-management-system' or similar, and check for version indicators in README, composer.json, or index files.
    Affected if The application directory contains itsourcecode or Admerc Event Management System files, and version 1.0 is indicated.
  2. Confirm the vulnerable script exists
    Locate the /admin/manage_user.php file within the web application directory structure. This is the specific file containing the SQL injection vulnerability.
    Affected if The file /admin/manage_user.php exists in your deployment.
  3. Verify the application is network-accessible
    Determine if the web application is accessible over the network. Check if the /admin/ endpoint responds to HTTP requests from potential attackers.
    Affected if The application and specifically the /admin/manage_user.php endpoint is externally or internally accessible via HTTP/HTTPS.
  4. Check for input processing on the ID parameter
    Examine whether the manage_user.php script processes a parameter named 'ID' or 'id' from GET or POST requests. This parameter is the injection point for the SQL vulnerability.
    Affected if The script accepts and processes an 'ID' parameter without proper parameterization.
  5. Assess if basic input validation is present
    Review application logs or test the ID parameter with non-numeric input to determine if any input validation, WAF, or other security controls are protecting the database queries.
    Affected if No input validation, prepared statements, or WAF protection is observed on the ID parameter in manage_user.php.

You are affected if Admerc/itsourcecode Event Management System version 1.0 is deployed, the /admin/manage_user.php file exists, and the ID parameter accepts user input without parameterized queries or input validation.

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

Implement prepared statements/parameterized queries for all database operations, particularly on the ID parameter in manage_user.php; apply input validation and least-privilege database accounts as defense-in-depth measures.

Fix this in Event Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

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