Skip to main content
VulnerabilityPublished Updated

CVE-2025-41002: MANANTIAL DE IDEAS Infoticketing · SQL Injection

Affects MANANTIAL DE IDEAS InfoticketingSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
MANANTIAL DE IDEASInfoticketingAffected
  • =all versions
Fixed in–

AI-suggested

Given the absence of official patches, organizations should immediately implement the following mitigations: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block malicious SQL injection payloads targeting the 'code' parameter in '/components/cart/cartApplyDiscount.php'. 2) Conduct thorough input validation and sanitization on all user-supplied data, especially the 'code' parameter, using parameterized queries or prepared statements to prevent injection. 3) Restrict database user privileges to the minimum necessary, avoiding use of high-privilege accounts for application database connections. 4) Monitor logs for unusual or suspicious POST requests to the vulnerable endpoint and set up alerts for potential exploitation attempts. 5) If feasible, isolate the Infoticketing application in a segmented network zone to limit lateral movement in case of compromise. 6) Engage with MANANTIAL DE IDEAS for updates or patches and plan for rapid deployment once available. 7) Consider temporary disabling or restricting access to the vulnerable functionality if business operations allow.

Description

SQL injection vulnerability in Infoticketing. This vulnerability allows an unauthenticated attacker to retrieve, create, update, and delete the database by sending a POST request using the 'code' parameter in '/components/cart/cartApplyDiscount.php'.

References

Community reviews

Loading reviews…