Loading vulnerability…
PuneethReddyHC event-management 1.0 contains an SQL injection vulnerability in its grocery product-search functionality. Improper handling of the sitem_name POST parameter permits crafted input to alter SQL query logic and disclose database contents. Successful exploitation may expose sensitive data and potentially compromise backend systems.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Python script (main.py) that serves as a proof-of-concept (POC) exploit for CVE-2025-65354. The script targets a web application endpoint at https://www.example.com/Grocery/search_products_itname.php, attempting to exploit a SQL injection vulnerability via the 'sitem_name' HTTP header. It sends three different POST requests with various SQL injection payloads and prints the full HTTP responses for each, allowing the user to analyze the results and determine if the vulnerability exists. The script is a basic POC and does not automate exploitation beyond detection. The only file in the repository is main.py, written in Python, and it requires the 'requests' and 'random' modules. The script is intended for manual analysis and verification of the SQL injection vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.