dbcve.org
Visitor Management SystemApplication · Projectworlds

CVE-2025-9047

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in projectworlds Visitor Management System 1.0. Affected is an unknown function of the file /visitor_out.php. The manipulation of the argument rid leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Visitor Management System 1.0 where the 'rid' parameter in /visitor_out.php is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in visitor_out.php, apply input validation on the 'rid' parameter, and conduct a broader code review for similar injection flaws. If a vendor patch exists, apply it immediately.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Visitor Management SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Visitor Management System installation
    Locate the web application directory and verify the presence of the Visitor Management System, typically found in web server document roots (e.g., /var/www/html/, C:\xampp\htdocs\, or similar). Look for application files indicating version 1.0.
    Affected if The Projectworlds Visitor Management System version 1.0 is installed on the server.
  2. Locate the vulnerable file
    Search for the file visitor_out.php within the web application directory structure. Common paths include /visitor_out.php or /include/visitor_out.php.
    Affected if The file visitor_out.php exists in the application installation.
  3. Verify the rid parameter is processed
    Examine the visitor_out.php file to confirm it processes a 'rid' parameter, typically via $_GET or $_POST request. Search for code patterns like $_REQUEST['rid'], $_GET['rid'], or $_POST['rid'].
    Affected if The file processes a 'rid' parameter without evidence of prepared statements or input validation.
  4. Check for SQL injection protection
    Review the visitor_out.php source code to determine if the 'rid' parameter is used in dynamic SQL queries without parameterization. Look for patterns like 'SELECT ... WHERE rid=' . $rid or similar string concatenation. If the code uses mysqli_prepare(), PDO prepared statements, or input validation/sanitization functions, the vulnerability may be mitigated.
    Affected if The rid parameter is used in SQL queries via string concatenation without prepared statements or input sanitization.
  5. Confirm application is exposed
    Verify the web application is accessible over the network (HTTP/HTTPS). SQL injection requires the vulnerable endpoint to be reachable.
    Affected if The visitor_out.php endpoint is accessible via HTTP/HTTPS from the network.

If the Projectworlds Visitor Management System 1.0 is installed, the visitor_out.php file exists, and the rid parameter is processed using dynamic SQL without prepared statements or input sanitization, the environment is affected by CVE-2025-9047.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in visitor_out.php, apply input validation on the 'rid' parameter, and conduct a broader code review for similar injection flaws. If a vendor patch exists, apply it immediately.

Fix this in Visitor Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9047 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data