CVE-2026-39112
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 · uneditedCross Site Scripting vulnerability in Apartment Visitors Management System Apartment Visitors Management System V1.1 in the visname parameter of visitors-form.php. An authenticated attacker can inject arbitrary JavaScript that is later executed when the malicious input is viewed in manage-newvisitors.php or visitor-detail.php.
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 confidenceA stored Cross Site Scripting (XSS) vulnerability exists in the Apartment Visitors Management System V1.1. An authenticated attacker can inject arbitrary JavaScript code via the visname parameter in visitors-form.php. The malicious payload is stored in the database and executes when administrative users view the visitor data in manage-newvisitors.php or visitor-detail.php.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Identify if Apartment Visitors Management System is installedLocate the web application's document root directory and check for visitors-form.php, manage-newvisitors.php, and visitor-detail.php files. Check any version information in README, about page, or source code headers.Affected if The application files visitors-form.php, manage-newvisitors.php, and visitor-detail.php exist in the environment.
-
Verify the visname parameter is accepted as inputLocate and inspect visitors-form.php to confirm it accepts a visname parameter. Check the form handling code to see how the visitor name is processed and stored.Affected if The visitors-form.php file exists and processes a visname parameter without visible sanitization.
-
Inspect database for stored XSS payloads in visitor recordsQuery the database table that stores visitor information (typically named 'visitors' or similar). Look for HTML or script tags in the visitor name field that may indicate exploitation.Affected if The database contains visitor records with unsanitized HTML or script tags in name-related fields.
-
Check if output pages render visitor names without encodingExamine the source code of manage-newvisitors.php and visitor-detail.php to determine if visitor names are output with proper HTML encoding (htmlspecialchars or equivalent).Affected if The manage-newvisitors.php or visitor-detail.php files render visitor names directly without HTML encoding.
The environment is affected if the Apartment Visitors Management System V1.1 is installed, the visname parameter in visitors-form.php accepts unsanitized input, and the output pages render visitor names without HTML encoding.
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 dataImplement strict input validation and sanitization on the visname parameter in visitors-form.php, and apply output encoding when rendering visitor names in manage-newvisitors.php and visitor-detail.php to prevent script execution.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39112 — 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-2026-39112 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