Skip to main content
VulnerabilityPublished Updated

CVE-2025-55444: SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediate code review and input validation: Developers should implement strict input validation and parameterized queries (prepared statements) for the id2 parameter to prevent SQL injection.
  2. Web Application Firewall (WAF): Deploy or update WAF rules to detect and block SQL injection attempts targeting the cancel_booking.php endpoint.
  3. Access controls: Restrict access to the cancel_booking.php page to authenticated and authorized users where possible, reducing the attack surface.
  4. Monitoring and logging: Enhance logging around database queries and web requests to detect anomalous activities indicative of SQL injection attempts.
  5. Network segmentation: Isolate the database server from direct internet access and limit connectivity to only necessary application servers.
  6. Incident response readiness: Prepare for potential exploitation by having backup and recovery procedures in place, and conduct threat hunting to identify any signs of compromise.
  7. Vendor engagement: Engage with the software vendor or project maintainers to expedite patch development and deployment.
  8. Temporary disablement: If feasible, temporarily disable the vulnerable functionality until a secure fix is available to prevent exploitation.

Description

A SQL injection vulnerability exists in the id2 parameter of the cancel_booking.php page in Online Artwork and Fine Arts MCA Project 1.0. A remote attacker can inject arbitrary SQL queries, leading to database enumeration and potential remote code execution.

References

Community reviews

Loading reviews…