CVE-2026-108968
Received Received - Intake

SQL Injection in Performance Indicator System 1.0

Publication date: 2026-10-13

Last updated on: 2026-10-13

Assigner: VulDB

Description
A weakness has been identified in SourceCodester Performance Indicator System 1.0. The affected element is an unknown function of the file /opils/staff/sales_history.php. This manipulation of the argument ID causes sql injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-13
Last Modified
2026-10-13
Generated
2026-10-13
AI Q&A
2026-10-13
EPSS Evaluated
N/A
NVD
CVE-2026-108968
EUVD
EUVD-2026-98288

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
SourceCodester Performance Indicator System 1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a SQL injection flaw in SourceCodester Performance Indicator System 1.0. The issue occurs in the sales_history.php file where the ID parameter is not properly validated or sanitized before being used in SQL queries. Attackers can inject malicious SQL code to manipulate the database without authentication.

Detection Guidance

To detect this SQL injection vulnerability, inspect the /opils/staff/sales_history.php file for improper handling of the ID parameter. Use tools like SQLmap to test for injection by sending crafted inputs such as ' OR 1=1 -- or time-based payloads like '; IF (1=1) WAITFOR DELAY '0:0:5'--. Monitor database logs for unusual queries or errors.

  • Test with SQLmap: sqlmap -u "http://target.com/opils/staff/sales_history.php?id=1" --batch --risk 3 --level 5
Impact Analysis

This vulnerability allows attackers to access, modify, or leak sensitive data from the database. They can also potentially take control of the system. Since no authentication is required, any user interacting with the affected system could be at risk of exploitation.

Compliance Impact

This vulnerability could lead to unauthorized access or leakage of sensitive data, violating GDPR and HIPAA requirements for data protection and confidentiality. Organizations using this system may face compliance violations, legal penalties, and reputational damage.

Mitigation Strategies

Immediately update the sales_history.php file to use prepared statements with parameter binding for all database queries. Validate and sanitize the ID parameter input strictly, rejecting any non-numeric values. Restrict database user permissions to the minimum required and audit all database access logs for suspicious activity.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-108968. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart