CVE-2026-26703
SQL Injection in Personnel Property Equipment System v1.0 Admin Module
Publication date: 2026-03-02
Last updated on: 2026-03-03
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jon-remus-sevellejo | personnel_property_equipment_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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 Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in sourcecodester Personnel Property Equipment System v1.0 is an SQL Injection issue located in the /ppes/admin/advance_search.php file. This means that the application does not properly sanitize user input in this part of the system, allowing an attacker to inject malicious SQL code.
How can this vulnerability impact me? :
An SQL Injection vulnerability can allow attackers to manipulate the database queries executed by the application. This can lead to unauthorized access to sensitive data, data modification or deletion, and potentially full control over the backend database.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'The vulnerability is an SQL Injection in the /ppes/admin/advance_search.php endpoint of the sourcecodester Personnel Property Equipment System v1.0. Detection typically involves sending crafted input to this endpoint to observe if SQL errors or unexpected behavior occurs.'}, {'type': 'paragraph', 'content': 'Common commands to detect SQL Injection include using curl or similar tools to send payloads that test for SQL injection, such as appending single quotes or SQL syntax to parameters in advance_search.php and checking the response for SQL errors or anomalies.'}, {'type': 'list_item', 'content': "Example curl command to test for SQL Injection: curl -i 'http://[target]/ppes/admin/advance_search.php?search=' OR '1'='1"}, {'type': 'list_item', 'content': 'Look for error messages or unexpected data in the response indicating SQL query manipulation.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying input validation and sanitization on all user inputs to the advance_search.php page to prevent malicious SQL code execution.
If possible, update or patch the Personnel Property Equipment System to a version where this vulnerability is fixed.
- Restrict access to the vulnerable endpoint to trusted users only.
- Use Web Application Firewalls (WAF) to detect and block SQL Injection attempts.