CVE-2019-9230
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 · uneditedAn issue was discovered on AudioCodes Mediant 500L-MSBR, 500-MBSR, M800B-MSBR and 800C-MSBR devices with firmware versions F7.20A to F7.20A.253. A cross-site scripting (XSS) vulnerability in the search function of the management web interface allows remote attackers to inject arbitrary web script or HTML via the keyword parameter.
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 search function of the management web interface on AudioCodes Mediant 500L-MSBR, 500-MBSR, M800B-MSBR, and 800C-MSBR devices running firmware versions F7.20A through F7.20A.253. The vulnerability allows remote attackers to inject arbitrary JavaScript or HTML code via the unsanitized keyword parameter in the search functionality.
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>= f7.20a, <= f7.20a.253>= f7.20a, <= f7.20a.253>= f7.20a, <= f7.20a.253>= f7.20a, <= f7.20a.253CVSS 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.0/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 management interface or use SNMP/CLI to retrieve the hardware model identifier. Look for model numbers 500L-MSBR, 500-MBSR, M800B-MSBR, or 800C-MSBR.Affected if The device is one of these four models: Mediant 500L-MSBR, 500-MBSR, M800B-MSBR, or 800C-MSBR
-
Check the installed firmware versionNavigate to the device web interface Status or About page, or use the CLI command 'show version' or 'software info' to retrieve the firmware version string.Affected if The firmware version is between F7.20A and F7.20A.253 inclusive
-
Verify the management web interface is enabledCheck the device network configuration settings via CLI or web interface to confirm that the HTTP/HTTPS management service is enabled and accessible from your network.Affected if The management web interface is enabled and reachable
-
Confirm search functionality accessLog into the management web interface and locate the search function. This is typically found in the administration or monitoring sections of the interface.Affected if The search functionality is present and accessible to authenticated users
The environment is affected if the device is a Mediant 500L-MSBR, 500-MBSR, M800B-MSBR, or 800C-MSBR running firmware F7.20A through F7.20A.253 with the management web interface and search function enabled.
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 dataUpgrade the device firmware to a version newer than F7.20A.253, which should contain proper input validation and output encoding for the search parameter. If an upgrade is not immediately possible, implement Web Application Firewall (WAF) rules to filter malicious XSS payloads in the keyword parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9230 — 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-2019-9230 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