Skip to main content
VulnerabilityPublished

CVE-2025-6890: code-projects Movie Ticketing System · SQL Injection

Affects code-projects Movie Ticketing SystemSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubez-lbz/pocpkg:github/ez-lbz/pocOther threatsAffected
  • =1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since no official patches are currently available, European organizations should implement immediate compensating controls. These include: 1) Applying strict input validation and sanitization on the 'Date' parameter at the web application firewall (WAF) or reverse proxy level to block malicious SQL payloads. 2) Employing parameterized queries or prepared statements within the application code to prevent SQL injection if source code access and modification are possible. 3) Restricting database user privileges to the minimum necessary to limit the impact of any successful injection. 4) Monitoring and logging all access to /ticketConfirmation.php and the 'Date' parameter for unusual or suspicious activity. 5) Conducting regular security assessments and penetration testing focused on injection vulnerabilities. 6) Planning for an urgent update or migration to a patched version once available. 7) Educating development and operations teams about secure coding practices and the risks of SQL injection. These targeted measures go beyond generic advice by focusing on the specific vulnerable parameter and the operational context of the affected system.

Description

A vulnerability was found in code-projects Movie Ticketing System 1.0. It has been rated as critical. This issue affects some unknown processing of the file /ticketConfirmation.php. The manipulation of the argument Date leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…