Security readout for executives and security teams
Plain-English summary
CVE-2020-36827 affects Perl applications using XAO::Web before 1.84. When JSON is embedded through Web::Action json-embed, angle brackets may not be handled safely, creating a browser-side injection risk if attacker-controlled content is included.
Executive priority
Treat this as a targeted remediation item, not an emergency. Prioritize internet-facing or authenticated user-facing Perl applications that use XAO::Web json-embed with user-supplied data.
Technical view
The issue is improper handling of < and > characters in JSON output generated by XAO::Web json-embed in Web::Action. The CVSS 3.1 score is 5.4, network-reachable, low complexity, low privileges required, with low confidentiality and integrity impact.
Likely exposure
Exposure is likely limited to Perl applications that depend on XAO::Web before version 1.84 and use Web::Action json-embed with content that may include user-controlled values.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. Practical risk depends on whether untrusted input reaches embedded JSON rendered by a browser.
Researcher notes
Evidence is narrow but consistent: the CVE description, affected version boundary, and upstream references point to unsafe angle-bracket handling in embedded JSON. No exploit status or broader affected product list is provided.
Mitigation direction
- Upgrade XAO::Web to version 1.84 or later.
- Review the upstream commit and changelog for the exact vendor fix.
- Reduce or remove json-embed use for untrusted content until upgraded.
- Retest pages that embed JSON into browser-rendered HTML.
Validation and detection
- Inventory Perl dependencies for XAO::Web versions before 1.84.
- Search application code for Web::Action json-embed usage.
- Trace whether user-controlled values can reach embedded JSON output.
- Confirm upgraded deployments no longer use the vulnerable module version.
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.
CWE-791: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-36827 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
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/amaltsev/XAO-Web/commit/20dd1d3bc5b811503f5722a16037b60197fe7ef4CVE reference
- https://metacpan.org/dist/XAO-Web/changesCVE reference
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.
Incomplete Filtering of Special Elements
Incomplete Filtering of Special Elements represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
