CVE-2026-129181: Visitor System SQL Injection
High CVSS (7.3) vulnerability; prioritize internet-facing assets.
TL;DR - CVE-2026-129181 is a CVSS 7.3 remote SQL injection vulnerability in projectworlds Visitor Management System 1.0. - The login endpoint reportedly mishandles the
Usernameparameter. No fixed version has been identified. - Public disclosure is reported, but active exploitation and a working public proof of concept are unconfirmed. - Administrators should remove unnecessary Internet exposure, investigate logs, preserve evidence, and seek a verified vendor fix.
Are You Affected?
CVE-2026-129181 affects projectworlds Visitor Management System 1.0. The reported vulnerable component is the login endpoint at /img/user%20page.php, where attacker-controlled data in the Username argument can reach a database query implemented with mysqli_query.
Organizations should also review related application and database assets when assessing exposure. For broader access-control context, see our guide to the best privileged access management tools.
| Field | Value |
|---|---|
| CVE ID | CVE-2026-129181 |
| CVSS base score | 7.3, High |
| CVSS vector | Not provided in the available NVD record |
| Attack vector | Remote |
| Authentication required | Not specified in the available NVD record |
| Affected product | projectworlds Visitor Management System |
| Affected version | 1.0 |
| Fixed version | None identified |
| Patch available | No verified vendor patch identified |
| CISA KEV status | Not listed |
The available record identifies version 1.0 as affected and does not identify additional versions. It also does not provide a confirmed fixed release. Organizations should not assume that a similarly named or later package is safe without verifying the actual source, release history, or vendor guidance.
This issue matters most to administrators who expose the application directly to the Internet. A remote SQL injection in a login endpoint can affect confidentiality and integrity even when the application is small or used only for internal visitor registration. Practical impact depends on database permissions, application behavior, network segmentation, and whether other services share the same database credentials.
The Fix, If You’re in a Hurry
No authoritative fixed version was identified in the available CVE material. The NVD record and available references identify Visitor Management System 1.0 as affected but do not confirm a patched release, fix commit, or vendor-supported upgrade path. Do not treat an unverified version number as a remediation.
Containment comes first:
- Remove the application from direct Internet exposure where possible.
- Restrict the login endpoint to trusted networks or an approved remote-access control.
- Place authentication and network controls in front of the application.
- Take the system offline if it is not required.
- Preserve logs before making changes if exploitation is suspected.
- Rotate application and database credentials if sensitive data may have been exposed.
Technical Notes
There is no verified upgrade command because no fixed version has been identified. For a deployment installed from a local application directory, first document the installation and back it up, then restrict access at the web-server or network layer. For example, an Apache configuration can limit the reported endpoint to an administrative network:
<Location "/img/user%20page.php">
Require ip 10.0.0.0/8
Require ip 192.168.0.0/16
</Location>
The exact configuration syntax depends on the web server and URL-decoding behavior. Test the rule against the application’s actual request path.
As an application-level remediation, replace string-concatenated SQL with a parameterized statement and validate the expected username format:
$stmt = $mysqli->prepare(
'SELECT id, username, password_hash FROM users WHERE username = ?'
);
$stmt->bind_param('s', $username);
$stmt->execute();
This code is a remediation pattern, not an official vendor patch. It must be integrated with the application’s authentication logic, error handling, password verification, and database schema.
Analyst’s Take: Treat the lack of confirmed exploitation as an uncertainty, not as a reason to leave the endpoint exposed. No fixed version or verified vendor patch is identified, so restricting access and preserving evidence are the most defensible first actions while the deployment and logs are reviewed.
How This Vulnerability Works
The reported root cause is unsafe handling of user-controlled input in a call to mysqli_query. The vulnerable input is identified as the Username argument on the login endpoint. If that value is incorporated into SQL text rather than passed as a bound parameter, specially crafted input can alter the intended query structure.
The exact SQL statement, database schema, and payload are not provided in the available record. Defenders should not assume a particular injection technique or database response. Depending on query construction and database permissions, exploitation could support authentication bypass, unauthorized data retrieval, modification of records, or abuse of other application functions that use the same database account.
A successful injection does not necessarily require a visible database error. Attackers may use boolean-based behavior, timing differences, or application responses to infer results. Web-application logs may therefore show requests that return normal HTTP status codes. Assess database errors, unusual response times, repeated login failures, and unexpected successful sessions together rather than treating them as isolated indicators.
Technical Notes
The vulnerable location is reported as:
/img/user%20page.php
The URL-encoded space is significant when searching logs. Depending on the web server, proxy, or logging format, the same request may appear as /img/user%20page.php, /img/user page.php, or a normalized path. Search for all representations and inspect the associated query string for the Username parameter.
A secure query should bind the username as data rather than concatenate it into SQL:
$username = $_POST['Username'] ?? '';
if (!preg_match('/\A[A-Za-z0-9_.@-]{1,128}\z/', $username)) {
http_response_code(400);
exit('Invalid username');
}
$stmt = $mysqli->prepare(
'SELECT id, username, password_hash FROM users WHERE username = ?'
);
$stmt->bind_param('s', $username);
$stmt->execute();
Input validation reduces noise and limits accepted values, but it is not a substitute for parameterized queries.
Severity, Explained
The available NVD data assigns CVE-2026-129181 a CVSS base score of 7.3, classified as High. The record describes the issue as remotely exploitable, which means an attacker may be able to send a crafted request over the network without local access to the server.
The complete CVSS vector is not included in the available NVD record. As a result, the exact values for attack complexity, privileges required, user interaction, scope, confidentiality impact, integrity impact, and availability impact cannot be independently stated. The record also does not specify the authentication requirement. Any explanation that assigns individual vector components would be inferential rather than confirmed.
Use the score as a prioritization signal, not as a complete risk assessment. A deployment with a database account that can read or modify sensitive visitor records presents greater practical risk than an isolated test instance with limited data. Internet exposure, weak administrative controls, shared credentials, and inadequate logging can all increase operational impact beyond what the base score communicates.
Is It Being Exploited?
The NVD description states that the exploit has been disclosed publicly and may be used. This supports treating the vulnerability as publicly disclosed. However, the available evidence does not establish confirmed active exploitation in the wild.
No verified working public proof of concept, dedicated GitHub exploit repository, or threat-intelligence report confirming exploitation was identified in the supplied research. The absence of a located proof of concept does not prove that no private exploit or informal payload exists. It means defenders should distinguish carefully between a public vulnerability record and independently confirmed exploitation.
CVE-2026-129181 is also not listed in the CISA Known Exploited Vulnerabilities catalog at the time of assessment. There is therefore no CISA KEV date, federal remediation deadline, required action, or ransomware-campaign flag associated with this CVE. KEV absence does not make the vulnerability safe; it only means that CISA has not listed it as a known exploited vulnerability in the referenced catalog.
Detecting It in Your Environment
Start by identifying every deployment of projectworlds Visitor Management System and determining whether version 1.0 is installed. Asset inventories may miss small PHP applications placed under a shared web root. Search web-server document roots, virtual hosts, container images, backup archives, and database inventories for application files and references to the Visitor Management System.
Review HTTP access logs for requests to the reported endpoint and inspect the Username parameter. Look for unexpected metacharacters, encoded quotes, SQL operators, comments, repeated requests with changing parameter values, and unusual response sizes or timing. Do not rely only on status code 500 responses: SQL injection attempts can return HTTP 200 responses when the application handles the request normally.
Technical Notes
A preliminary command-line search for common web-server log formats might look like this:
zgrep -Ei \
'(/img/(user%20page|user page)\.php|Username=|%27|%22|%2[79]|union([+%20]|%20)select|sleep\(|benchmark\(|--[+%20]|%23)' \
/var/log/apache2/access.log* /var/log/nginx/access.log*
This is a triage pattern, not a complete SQL injection detector. It can produce false positives and may miss requests if the parameter is POSTed, logged separately, or transformed by a reverse proxy.
For environments using an HTTP telemetry platform, a query can be adapted to the local schema. Conceptually:
http.path contains "/img/user"
and http.method in ("GET", "POST")
and (
url.query contains "Username="
or http.request.body contains "Username="
)
and (
http.request.body matches "(?i)(union|select|sleep|benchmark|or[+%20]+1[=]%5b?1|%27|%22|%2d%2d|%23)"
or url.query matches "(?i)(union|select|sleep|benchmark|%27|%22|%2d%2d|%23)"
)
Use the application’s real field names and decoded or raw URL representation. Correlate suspicious requests with authentication events, database audit logs, account changes, visitor-record modifications, and outbound connections from the web server.
If database logs are available, search for queries generated by the application account that contain unexpected SQL syntax or access tables outside the normal login workflow.
If exploitation is suspected, isolate the host or restrict the application while preserving volatile and persistent evidence. Rotate application, database, administrator, and user credentials that may have been exposed. Review database grants, inspect for unauthorized accounts or modified records, and compare application files against a known-good copy. A clean reinstall may be preferable to attempting to repair a potentially modified web root in place.
References and Further Reading
The primary technical record is the NVD entry for CVE-2026-129181. It identifies projectworlds Visitor Management System 1.0, the login endpoint, the Username argument, remote SQL injection, and a CVSS base score of 7.3. It does not provide the complete CVSS vector, exact query, fixed version, or a verified exploit payload.
For background on another class of network security vulnerability, see what a sidecar proxy is. It is unrelated to CVE-2026-129181 but may be useful when reviewing application traffic architecture and service-to-service controls.
Available references include:
- NVD search and CVE record
- VulDB CVE record
- VulDB submission record
- VulDB vulnerability record
- VulDB CTI reference
- GitHub Advisory Database search
- CISA Known Exploited Vulnerabilities Catalog
The VulDB pages returned HTTP 403 during the referenced research, so their underlying details could not be independently verified. The GitHub search context did not confirm a dedicated advisory, patch release, or exploit repository. Administrators should verify any future vendor announcement or release against an authoritative project source before upgrading, and should continue treating version 1.0 as affected until a supported fix is confirmed.
This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.