Quick answers
- Is CVE-2026-112141 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112141 being exploited in the wild.
- How severe is CVE-2026-112141?
- High severity, with a CVSS score of 7.3, published 19 October 2026.
- Which products and versions are affected?
- Satya-Vinay Events-Management-System up to commit 437c77ceb69bf9fe2e3f4f46f7871b83f425383a.
- Is there a fix for CVE-2026-112141?
- No fixed version is recorded yet. Use parameterized prepared statements (mysqli prepared statements) for all database queries, implement input validation and escaping, and add authentication checks before allowing registration modification.</anigation> </invoke> If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-112141 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-112141?
- Check whether you run Satya-Vinay Events-Management-System at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Use parameterized prepared statements (mysqli prepared statements) for all database queries, implement input validation and escaping, and add authentication checks before allowing registration modification.</anigation> </invoke>
Technical details
SQL injection in the doedit.php Registration-Edit Handler component allows unauthenticated remote code execution via unescaped $_REQUEST parameters (id, name, title, year, gender, fromdate, todate, people) passed directly into mysqli_query UPDATE statements. The attacker can inject a comment character (#) to truncate the WHERE clause and apply modifications to all table rows, or inject subqueries to exfiltrate or corrupt data. No authentication or parameterized queries are used.
Affected products
- satya-vinay Events-Management-System up to commit 437c77ceb69bf9fe2e3f4f46f7871b83f425383a
Timeline
- 2026-10-04: disclosed: Vulnerability reported via GitHub issue
- 2026-10-19: advisory