Security readout for executives and security teams
Plain-English summary
FusionPBX 4.4.1 has a reported cross-site scripting issue in a dialplan editing page. An attacker could inject script or HTML through the dialplan_uuid parameter. The sources do not provide CVSS, authentication requirements, or confirmed real-world exploitation, so urgency depends on whether FusionPBX 4.4.1 is deployed and reachable.
Executive priority
Treat this as a targeted application security issue, not a confirmed emergency. If FusionPBX 4.4.1 is internet-reachable or broadly accessible internally, prioritize validation and remediation because XSS can support account compromise or unauthorized actions in privileged web sessions.
Technical view
CVE-2019-19388 describes XSS in app/dialplans/dialplan_detail_edit.php in FusionPBX 4.4.1 via dialplan_uuid. The CVE metadata does not include CWE, CVSS, normalized affected CPEs, or exploit prerequisites. A FusionPBX commit is referenced, indicating upstream code changed, but the supplied data does not define a release-level fix.
Likely exposure
Exposure is likely limited to organizations running FusionPBX 4.4.1, especially where administrative or dialplan management interfaces are reachable by untrusted users. The source bundle does not state whether authentication is required.
Exploitation context
The bundle marks CISA KEV as false and provides no cited evidence of active exploitation. A public gist is referenced, but the supplied bundle does not include its contents, so exploit maturity cannot be confirmed from the provided data.
Researcher notes
Key gaps are missing CVSS, CWE, authentication context, affected CPEs, and release mapping. The description identifies the parameter and file, but validation should avoid assuming exploitability beyond source evidence. Use the referenced upstream commit to understand the precise code change.
Mitigation direction
- Identify any FusionPBX 4.4.1 instances in production or staging.
- Review FusionPBX vendor guidance and the referenced commit for the corrected code path.
- Restrict access to FusionPBX administrative interfaces to trusted networks and users.
- Prioritize upgrade planning if deployed systems match the described vulnerable version.
Validation and detection
- Confirm whether app/dialplans/dialplan_detail_edit.php exists on deployed FusionPBX systems.
- Check the installed FusionPBX version against 4.4.1 and later vendor releases.
- Review whether the referenced commit is present in deployed source code.
- Inspect web logs for unusual requests to dialplan_detail_edit.php involving dialplan_uuid.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-19388 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://gist.github.com/xax007/28e7326acfae677be0b351216888e522CVE reference · x_refsource_MISC
- https://github.com/fusionpbx/fusionpbx/commit/b584973e73a4d25be623c9748dd9817f69422eccCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.