Skip to main content
CVE-2025-65354VulnerabilityPublished Updated

CVE-2025-65354: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Dec 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 2026-10-25.

What to do

AI-suggested

1. Implement Web Application Firewall (WAF) rules specifically designed to detect and block SQL injection attempts targeting the sitem_name parameter in /Grocery/search_products_itname.php. 2. Apply input validation and sanitization at the application level, ensuring all user-supplied data is properly escaped or parameterized before database queries. 3. Employ prepared statements with parameterized queries to eliminate direct concatenation of user input into SQL commands. 4. Restrict database user permissions to the minimum necessary, preventing execution of administrative commands even if injection occurs. 5. Monitor application logs and network traffic for unusual query patterns or repeated failed attempts indicative of exploitation attempts. 6. If possible, isolate the vulnerable application environment from critical internal networks to limit lateral movement. 7. Engage with the software vendor or developer community to obtain or request patches and updates addressing this vulnerability. 8. Conduct regular security assessments and penetration testing focusing on injection flaws to proactively identify and remediate similar issues.

Description

Improper input handling in /Grocery/search_products_itname.php inPuneethReddyHC event-management 1.0 permits SQL injection via the sitem_name POST parameter. Crafted payloads can alter query logic and disclose database contents. Exploitation may result in sensitive data disclosure and backend compromise.

References

Community reviews

Loading reviews…