CVE-2025-8947
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 · uneditedA vulnerability was found in projectworlds Visitor Management System 1.0. This issue affects some unknown processing of the file /query_data.php. The manipulation of the argument dateF/dateP leads to sql injection. The attack may be initiated 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 confidenceThe projectworlds Visitor Management System 1.0 contains a SQL injection vulnerability in /query_data.php where the dateF and dateP parameters are not properly sanitized before being used in SQL queries. An attacker can inject malicious SQL commands through these parameters to extract, modify, or delete database contents. The CVSS 9.8 score reflects the critical nature of remote, unauthenticated SQL injection allowing full database compromise.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Projectworlds Visitor Management System installationLocate the web application files in your web server root directory. Look for typical indicators such as a 'visitor' or 'vms' folder, or search for files containing 'visitor management' or Projectworlds branding.Affected if The application is deployed on your server.
-
Identify the installed versionCheck for a version file, about page, or any file containing version metadata. Look in README files, config files, or the main index.php for a version string. The affected version is exactly 1.0.Affected if The installed version is 1.0.
-
Locate the vulnerable scriptSearch the web root for the file query_data.php. This file should exist in the application's web-accessible directory.Affected if query_data.php exists in the application directory.
-
Verify the vulnerable parameters are in useOpen query_data.php and inspect the code around lines where $dateF and $dateP variables are used in SQL queries. Look for direct concatenation of these parameters into SQL statements without prepared statements, binding, or escaping functions.Affected if The dateF and dateP parameters are directly interpolated into SQL queries without sanitization.
If you are running Projectworlds Visitor Management System version 1.0 with query_data.php accessible and the dateF/dateP parameters are used in unsanitized SQL queries, your environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataApply parameterized queries (prepared statements) for all SQL queries in query_data.php, specifically sanitizing or using bound parameters for the dateF and dateP arguments. Alternatively, implement proper input validation and escaping for date parameters before query execution.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-8947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8947 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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