CVE-2025-2353
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, which was classified as critical, was found in VAM Virtual Airlines Manager up to 2.6.2. Affected is an unknown function of the file /vam/index.php of the component HTTP GET Parameter Handler. The manipulation of the argument ID/registry_id/plane_icao leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well. The vendor was contacted early about this disclosure but did not respond in any way.
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 VAM Virtual Airlines Manager up to version 2.6.2 allows remote attackers to inject malicious SQL queries via GET parameters (ID, registry_id, plane_icao) in /vam/index.php. The HTTP GET Parameter Handler fails to properly sanitize these parameters before using them in 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm VAM Virtual Airlines Manager is installedLook for the presence of the /vam/ directory in your web root, or check the application response at your VAM installation URLAffected if The /vam/index.php file exists and responds to HTTP requests
-
Check the installed versionAccess the VAM admin panel, About page, or check version.php if it exists in the installation directory. Compare the version number to 2.6.2Affected if The installed version is 2.6.2 or lower
-
Verify the vulnerable parameters are processedCheck if your application processes GET parameters named 'ID', 'registry_id', or 'plane_icao' through /vam/index.php. Review the application code or test by observing parameter handlingAffected if The application accepts and processes these GET parameters in the vulnerable endpoint
-
Confirm lack of parameterized queries in the codeReview the source code of /vam/index.php and related files for direct use of $_GET['ID'], $_GET['registry_id'], or $_GET['plane_icao'] in SQL queries without prepared statementsAffected if These parameters are used directly in SQL queries without parameter binding
Your environment is affected if you are running VAM Virtual Airlines Manager version 2.6.2 or lower and the application processes ID, registry_id, or plane_icao GET parameters through /vam/index.php in unparameterized SQL queries.
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/parameterized queries for all database operations involving user-supplied input. Audit all parameters in /vam/index.php and related files for SQL injection vulnerabilities and apply input validation.
- Consultation3.0 h
- Implementation8.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 $4,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2353 — 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-2025-2353 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