Skip to main content

Employee Movement Tracking EUVDEUVD-2026-92963

| CVE-2026-105776 MEDIUM
SQL Injection (CWE-89)
2026-10-06 VulDB GHSA-3mhp-8pwr-cm2j
5.5
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Locate exposed /admin_transaction.php
  2. Exploit
    Craft malicious Username parameter
  3. Execution
    Inject SQL via unsanitized input
  4. Impact
    Extract or alter database records

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a reachable deployment of the Employee-Movement-Tracking-and-Monitoring-Website-for-IOCL application with the /admin_transaction.php endpoint accessible to the attacker; exploitation injects SQL through the Username argument. The supplied CVSS vector (PR:N/UI:N) indicates no authentication or user interaction is needed, but the endpoint's 'admin_' naming implies it may be intended for an authenticated administrative session - defenders should confirm whether the page is reachable pre-authentication. The primary limiting factor is deployment scarcity: this is a rolling-release hobby project with no packaged versions and a tiny install base, so realistic exposure depends on finding one of the few public instances.

Impact

Signals conflict on paper but converge on low practical priority. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes an easy, remote, unauthenticated attack, and a public exploit exists (VulDB, E:P 'Proof-of-Concept'), which normally raises urgency. However, the vulnerable-system impacts are all rated Low (VC:L/VI:L/VA:L) with no subsequent-system impact, yielding a modest 6.9 base score, and the affected software is an obscure single-developer GitHub project (bhagya3929/Employee-Movement-Tracking-and-Monitoring-Website-for-IOCL). No EPSS score, no CISA KEV listing, and no SSVC decision data were provided, so there is no evidence of real-world or widespread exploitation. Note a tension between the metadata and the artifact: the vulnerable endpoint is named /admin_transaction.php, implying an administrative context, yet the vector asserts PR:N (unauthenticated) - this should be verified against the actual code, as PR:N may be optimistic if the endpoint sits behind an admin login. Overall this reads as a high-CVSS-but-low-real-risk issue: credible and exploitable in a lab, but with negligible deployment footprint and no confirmed active abuse.

Exploit ScenarioDerived

A remote attacker locates an internet-exposed instance of the IOCL employee-movement-tracking web application and sends a crafted request to /admin_transaction.php, injecting SQL metacharacters into the Username argument. Because the input is concatenated into a database query (CWE-89), the attacker reads or manipulates database records. A public proof-of-concept exploit has been published via the project's GitHub issue tracker, lowering the skill required.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

SQL injection in the Employee Movement Tracking and Monitoring Website for IOCL (a PHP project published at github.com/bhagya3929) allows remote attackers to manipulate the Username argument of /admin_transaction.php and inject arbitrary SQL. Per the supplied CVSS vector (AV:N/AC:L/PR:N/UI:N, E:P), no authentication or user interaction is required and publicly available exploit code exists, though the 'admin_' endpoint naming means defenders should verify whether the page is actually reachable pre-authentication. The impact is assessed as limited data confidentiality, integrity, and availability loss (VC:L/VI:L/VA:L), and practical priority is low because the project is a rolling-release hobby application with no packaged versions and a very small install base - exploitation depends on finding one of the few publicly reachable deployments. The maintainer was notified via a GitHub issue but has not responded, and no vendor-released patch has been identified.

RemediationAI

No vendor-released patch has been identified at time of analysis - the project maintainer has not responded to the GitHub issue (https://github.com/bhagya3929/Employee-Movement-Tracking-and-Monitoring-Website-for-IOCL/issues/1) that reported the flaw, and the rolling-release model means no fixed version number can be cited; track the repository and the VulDB entry (https://vuldb.com/vuln/413810) for an upstream commit, and treat any upstream fix as a PR/commit rather than a tagged release. Until then, apply compensating controls specific to this endpoint: require authentication and session validation before /admin_transaction.php executes any SQL (trade-off: legitimate unauthenticated flows, if any, break, but the admin_ naming suggests this is the intended state anyway), and restrict reachability of /admin_transaction.php to trusted networks or administrative IP ranges via web server ACLs or a reverse proxy (trade-off: remote administration becomes VPN-dependent). Rewrite the Username handling to use parameterized/prepared statements or strict allow-list validation (e.g., accept only expected username character sets and lengths) rather than concatenating input into the query - this is the only control that removes the root cause and should be backported locally if you cannot wait for upstream. As a defense-in-depth layer with no redesign, deploy a WAF rule set that flags SQL metacharacters and comment sequences in the Username parameter of /admin_transaction.php (trade-off: false positives against unusual but legitimate usernames and no protection if the WAF is bypassed or the instance is directly reachable). Finally, reduce blast radius on the backend by ensuring the application's database account has only the privileges the app needs (drop DROP/ALTER/GRANT rights) and by removing access to any sensitive tables the tracking app does not use - this limits the impact of a successful injection but does not prevent it.

Affected VersionsENISA

Employee-Movement-Tracking-and-Monitoring-Website-for-IOCL ae783195ba7e0390d3b3bfaddd99944b7e9735a4

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is a PHP web application - the Employee-Movement-Tracking-and-Monitoring-Website-for-IOCL - whose /admin_transaction.php script takes a Username parameter and interpolates it into a SQL statement without proper neutralization, the classic CWE-89 improper neutralization of special elements used in an SQL command. Because the parameter reaches a backend database query directly, an attacker can restructure the query (for example with tautologies, UNION selection, or stacked statements depending on the DB driver) to read, alter, or damage data the application can access. The CPE cpe:2.3:a:bhagya3929:employee-movement-tracking-and-monitoring-website-for-iocl:*:*:*:*:*:*:*:* carries wildcard version fields, confirming that the vendor ships this code only as a continuously updated rolling release from the GitHub repository (current snapshot ae783195ba7e0390d3b3bfaddd99944b7e9735a4) rather than as tagged, packaged versions - so no clean 'affected' versus 'fixed' version boundary exists and every deployment of the repository at or before that commit must be treated as potentially vulnerable. The 'admin_' prefix in the script name implies an administrative workflow, which is a relevant nuance: the CVSS vector asserts PR:N, but the intended deployment may sit behind an authenticated session, so pre-auth reachability is a deployment-specific question rather than a confirmed property.

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 5.5 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 7.3 HIGH

Remote SQLi over the network with low complexity and no interaction; PR:N retained per input vector despite the admin-endpoint naming, with partial C/I/A reflecting limited single-table database impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
CVSS changed
Oct 06, 2026 - 07:22 NVD
6.9 (MEDIUM) 5.5 (MEDIUM)
CVE Published
Oct 06, 2026 - 06:00 cve.org
MEDIUM 6.9

DescriptionCVE.org

A flaw has been found in bhagya3929 Employee-Movement-Tracking-and-Monitoring-Website-for-IOCL up to ae783195ba7e0390d3b3bfaddd99944b7e9735a4. Affected by this vulnerability is an unknown functionality of the file /admin_transaction.php. This manipulation of the argument Username causes sql injection. It is possible to initiate the attack remotely. The exploit has been published and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Threat Intelligence Overview

EPSS Score
0.3%
Top 76% exploitable
Prevalence
Rare
obscure single-developer GitHub project, no enterprise or commercial footprint
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy