dbcve.org
InjectionWeakness · CWE-74

CVE-2026-14795

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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 CodeAstro Apartment Visitor Management System 1.0. Affected by this issue is some unknown functionality of the file /apartment-visitor/action-visitor.php. Such manipulation of the argument remark leads to sql injection. The attack may be performed from remote. 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 CodeAstro Apartment Visitor Management System 1.0 allows remote attackers to inject malicious SQL queries through the 'remark' parameter in /apartment-visitor/action-visitor.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries for the remark parameter, implement proper input validation, and apply principle of least privilege to the database user. As an interim measure, deploy a WAF rule to block SQL injection patterns.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 CodeAstro Apartment Visitor Management System is installed
    Locate the web application files on the server - typically found in the web root directory under a folder named 'apartment-visitor' or similar. Check for the presence of action-visitor.php.
    Affected if The application is present on the server and the vulnerable file exists.
  2. Verify the application version
    Check the application for a version identifier - often found in a readme.txt, version file, or within the PHP source code comments/headers. Compare against version 1.0.
    Affected if The installed version is 1.0 or falls within the affected version range.
  3. Locate the vulnerable PHP file
    Search for the file /apartment-visitor/action-visitor.php in the web application directory structure. This is the specific file containing the SQL injection vulnerability.
    Affected if The file action-visitor.php exists in the apartment-visitor directory.
  4. Check if application is network-accessible
    Determine if the web server hosting the application accepts remote connections. Test by accessing the application's login or main page over HTTP/HTTPS from an external host.
    Affected if The application is accessible from remote/network sources, making the SQL injection exploitable remotely.
  5. Inspect the vulnerable parameter handling
    Review the action-visitor.php source code and locate the 'remark' parameter handling. Look for direct use of this parameter in SQL queries without prepared statements or sanitization functions.
    Affected if The code shows the 'remark' parameter is used directly in SQL queries without parameterized queries or input sanitization.

A user is affected if CodeAstro Apartment Visitor Management System version 1.0 is installed, the file action-visitor.php exists, and the application is accessible, with the 'remark' parameter handled unsafely in SQL 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 prepared statements/parameterized queries for the remark parameter, implement proper input validation, and apply principle of least privilege to the database user. As an interim measure, deploy a WAF rule to block SQL injection patterns.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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