CVE-2026-108968: SourceCodester Performance Indicator System SQL injection in sales_history

CVE-2026-108968 · Severity: high · CVSS 7.3 · Published 2026-10-13

SourceCodester Performance Indicator System is a PHP-based application for tracking sales performance metrics. An unauthenticated attacker can inject malicious SQL commands through the ID parameter in the sales history page, allowing them to read, modify, or delete sensitive database records without authorization.

Technologies: SourceCodester Performance Indicator System. Vendors: SourceCodester.

Quick answers

Is CVE-2026-108968 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-108968 being exploited in the wild.
How severe is CVE-2026-108968?
High severity, with a CVSS score of 7.3, published 13 October 2026.
Which products and versions are affected?
SourceCodester Performance Indicator System 1.0.
Is there a fix for CVE-2026-108968?
No fixed version is recorded yet. Use prepared statements and parameterized queries to separate SQL code from user input. Strictly validate and filter the 'id' parameter to ensure it conforms to expected format (e.g., numeric only), and configure the database account with minimal necessary permissions to limit damage from successful injection. 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-108968 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-108968?
Check whether you run SourceCodester Performance Indicator 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 prepared statements and parameterized queries to separate SQL code from user input. Strictly validate and filter the 'id' parameter to ensure it conforms to expected format (e.g., numeric only), and configure the database account with minimal necessary permissions to limit damage from successful injection.

Technical details

A SQL injection vulnerability exists in /opils/staff/sales_history.php due to insufficient input validation on the 'id' parameter, which is directly concatenated into SQL queries. Remote unauthenticated attackers can exploit this via time-based blind, boolean-based blind, or union-based SQL injection to access or manipulate the backend database. The vulnerability requires network access but no prior authentication or user interaction.

Affected products

  • SourceCodester Performance Indicator System 1.0

Timeline

  • 2026-09-25: disclosed
  • 2026-10-13: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.