dbcve.org
Online Apartment Visitor Management SystemApplication · Campcodes

CVE-2025-11350

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-07
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 security flaw has been discovered in Campcodes Online Apartment Visitor Management System 1.0. The affected element is an unknown function of the file /bwdates-reports-details.php. The manipulation of the argument fromdate/todate results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.

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 · moderate confidence

SQL injection vulnerability in Campcodes Online Apartment Visitor Management System 1.0 affecting the /bwdates-reports-details.php file. The fromdate and todate parameters are not properly sanitized before being used in database queries, allowing attackers to inject arbitrary SQL code remotely.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the fromdate and todate parameters. Implement proper input validation and escaping. Apply vendor patch if available.

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
Online Apartment 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 the vulnerable application is installed
    Locate the file /bwdates-reports-details.php in your web server document root or application directory. Common paths may include /var/www/html/, /www/, or C:\inetpub\wwwroot\ depending on your OS and web server configuration.
    Affected if The file exists and is part of a Campcodes Online Apartment Visitor Management System installation
  2. Verify the application version is 1.0
    Check your application documentation, about page, or version file for the installed version of Campcodes Online Apartment Visitor Management System. Compare your installed version to the affected range.
    Affected if The installed version is 1.0 exactly
  3. Confirm the application is accessible via web
    Attempt to access the affected endpoint by making an HTTP request to http://[your-server]/bwdates-reports-details.php
    Affected if The page loads and responds to requests, indicating the vulnerable code is accessible
  4. Identify if fromdate and todate parameters are processed
    Review the source code of bwdates-reports-details.php or test the endpoint by sending a request with values in the fromdate and todate parameters (e.g., ?fromdate=2025-01-01&todate=2025-12-31)
    Affected if The application accepts and processes these parameters in SQL queries without proper sanitization
  5. Check for lack of parameterized queries
    Inspect the application source code around the database query logic in bwdates-reports-details.php. Look for how fromdate and todate are incorporated into SQL statements.
    Affected if The code directly concatenates or interpolates these parameter values into SQL queries without using prepared statements or binding parameters
  6. Test for SQL injection response differences
    Send benign test payloads to fromdate and todate parameters and observe database error messages or abnormal application behavior (e.g., single quote injection: fromdate=')
    Affected if The application returns SQL syntax errors or unexpected results indicating unsanitized input is being executed as SQL code

You are affected if you have Campcodes Online Apartment Visitor Management System version 1.0 running with the bwdates-reports-details.php file accessible and the fromdate/todate parameters processed without parameterized queries.

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 for the fromdate and todate parameters. Implement proper input validation and escaping. Apply vendor patch if available.

Fix this in Online Apartment Visitor Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11350 — 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-11350 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