CVE-2023-22296
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 · uneditedReflected cross-site scripting vulnerability in MAHO-PBX NetDevancer series MAHO-PBX NetDevancer Lite/Uni/Pro/Cloud prior to Ver.1.11.00, MAHO-PBX NetDevancer VSG Lite/Uni prior to Ver.1.11.00, and MAHO-PBX NetDevancer MobileGate Home/Office prior to Ver.1.11.00 allows a remote unauthenticated attacker to inject an arbitrary script.
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 confidenceThis is a reflected cross-site scripting (XSS) vulnerability in the web interface of MAHO-PBX NetDevancer series devices (Lite, Uni, Pro, Cloud, VSG, and MobileGate Home/Office versions prior to 1.11.00). A remote unauthenticated attacker can inject arbitrary JavaScript code through unsanitized user input that gets reflected back in HTTP responses, potentially allowing session hijacking or credential theft.
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.11.00< 1.11.00< 1.11.00CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 the device modelAccess the device's web interface or check the device documentation/label to confirm it is a Maho Pbx NetDevancer product (Lite, Uni, Pro, Cloud, VSG, or MobileGate Home/Office)Affected if The device is a NetDevancer series product
-
Check the firmware versionLog into the web interface and navigate to the system status or firmware information page, or use the command line interface (CLI) to run 'show version' or similar command to retrieve the installed firmware versionAffected if The firmware version is below 1.11.00
-
Confirm web interface is accessibleAttempt to reach the device's HTTP/HTTPS web interface from a client machine by entering the device IP address in a web browserAffected if The web interface is exposed and reachable over the network
-
Identify reflected parameters in HTTP responsesUse a web proxy or browser developer tools to capture HTTP requests and responses. Submit various user-supplied inputs (such as in login forms, search fields, or URL parameters) and observe if the same values are reflected verbatim in the response without proper encoding or sanitizationAffected if User input is reflected in HTTP responses without encoding, indicating potential XSS vulnerability
The environment is affected if it is a Maho Pbx NetDevancer device (Lite, Uni, Pro, Cloud, VSG, or MobileGate Home/Office) running firmware version below 1.11.00 with the web interface accessible and unsanitized user input reflected in responses.
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.
dbcve · scoped1.11.00
Upgrade to version 1.11.00 or later which contains the security patch. If immediate patching is not possible, implement web application firewall (WAF) rules to filter malicious script payloads in HTTP requests.
Maho Pbx Netdevancer series (Firmware, VSG, MobileGate) version 1.11.00
- Obtain the firmware version 1.11.00 from the official vendor (Maho Pbx/ATE Mahoroba)
- Review vendor release notes for any specific upgrade instructions
- Backup current configuration before proceeding with upgrade
- Upload and install firmware version 1.11.00 following vendor-provided procedures
- Verify successful installation and confirm the system is operational
- Validate that the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22296 — 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-2023-22296 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