dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-32843

MEDIUM · 5.1 CVSS v4.0 Published 2026-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Location Aware Sensor System by Linkit ONE, up to commit f06bd20 (2023-04-26), contains a reflected cross-site scripting vulnerability in the PM25.php file that allows remote attackers to execute arbitrary JavaScript by injecting malicious code into GET parameters. Attackers can craft a malicious URL containing unencoded payloads in the site, city, district, channel, or apikey parameters to execute scripts in victims' browsers when they visit the page.

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

A reflected cross-site scripting vulnerability exists in the PM25.php file of the Location Aware Sensor System. The application fails to properly sanitize user-supplied GET parameters (site, city, district, channel, apikey) before reflecting them in the HTML output, allowing attackers to inject malicious JavaScript that executes in victims' browsers.

MitigationImplement proper input validation and output encoding for all GET parameters before rendering them in HTML pages. Use context-appropriate encoding functions (such as htmlspecialchars() in PHP) to neutralize script injection attempts.

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
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Locate PM25.php file
    Search the web root or application directory for the file PM25.php (e.g., `find /var/www -name PM25.php` on Linux or search in the project directory on Windows)
    Affected if PM25.php file exists in the application directory structure
  2. Confirm application identity
    Check if the application containing PM25.php is the Location Aware Sensor System by reviewing application documentation, headers, or the source code comments in PM25.php
    Affected if The application is the Location Aware Sensor System
  3. Inspect vulnerable parameter handling
    Open PM25.php and examine how the GET parameters (site, city, district, channel, apikey) are processed - look for direct echo or print statements that output these parameters without using sanitization functions like htmlspecialchars()
    Affected if The code reflects any of these GET parameters directly into HTML output without proper encoding
  4. Test for XSS reflection
    Send a crafted HTTP GET request to PM25.php with a benign XSS test payload in one of the parameters (e.g., `?site=<script>alert(1)</script>`) and inspect the response to see if the payload is rendered unescaped
    Affected if The test payload appears literally in the HTML response without being escaped
  5. Verify web accessibility
    Check web server configuration to confirm PM25.php is accessible over HTTP/HTTPS (check routing, .htaccess, or nginx config)
    Affected if PM25.php is accessible via web requests and processes user-supplied parameters

If PM25.php exists as part of the Location Aware Sensor System and reflects any of the GET parameters (site, city, district, channel, apikey) in HTML without sanitization, the environment is affected by this reflected XSS vulnerability.

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

Implement proper input validation and output encoding for all GET parameters before rendering them in HTML pages. Use context-appropriate encoding functions (such as htmlspecialchars() in PHP) to neutralize script injection attempts.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

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