dbcve.org
Online Flight Booking Management SystemApplication · Campcodes

CVE-2025-8952

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-14
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
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 Campcodes Online Flight Booking Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/ajax.php?action=login of the component Login. The manipulation of the argument Username leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the 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 the login functionality of Campcodes Online Flight Booking Management System 1.0. The Username parameter in /admin/ajax.php?action=login is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. This pre-authentication flaw with CVSS 9.8 enables complete database compromise.

MitigationImplement parameterized queries/prepared statements for all SQL operations, particularly in the login function. Validate and sanitize all user inputs, apply principle of least privilege to database accounts, and deploy a WAF as an interim control.

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
Online Flight Booking 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 application installation
    Locate the file /admin/ajax.php on the web server. This is the entry point containing the vulnerable login function. Use file system search or check web root directories.
    Affected if The file /admin/ajax.php exists and the application is Campcodes Online Flight Booking Management System.
  2. Verify the installed version
    Check the application version. In Campcodes Online Flight Booking Management System, the version is typically displayed in the admin dashboard footer, about page, or a version file. Compare against the affected version 1.0.
    Affected if The installed version is exactly 1.0, matching the sole affected version listed.
  3. Confirm login endpoint accessibility
    Access the URL path /admin/ajax.php?action=login in a web browser or via curl to verify the login function is reachable without authentication.
    Affected if The login endpoint responds and accepts input without requiring prior authentication.
  4. Inspect the Username parameter handling in source code
    Open /admin/ajax.php and locate the code handling the 'login' action. Find the section processing the Username input field. Examine whether the code uses prepared statements/parameterized queries or direct string concatenation when building the SQL query.
    Affected if The code uses direct string concatenation or unsanitized variable interpolation in the SQL query for the Username field, rather than prepared statements.
  5. Check database query construction
    In the login function code, identify the exact SQL query string used for authentication. Look for patterns like "SELECT * FROM ... WHERE username='" + $username + "'" or similar non-parameterized constructions.
    Affected if The SQL query construction does not use bind parameters, prepared statements, or input escaping for the Username field.

The environment is affected if Campcodes Online Flight Booking Management System version 1.0 is installed and the login function at /admin/ajax.php?action=login processes the Username parameter 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

Implement parameterized queries/prepared statements for all SQL operations, particularly in the login function. Validate and sanitize all user inputs, apply principle of least privilege to database accounts, and deploy a WAF as an interim control.

Fix this in Online Flight Booking Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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