CWE-91
Allowed-with-ReviewXML Injection (aka Blind XPath Injection)
Abstraction: Base · Status: Draft
The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system.
216 vulnerabilities reference this CWE, most recent first.
CVE-2020-8479 (GCVE-0-2020-8479)
Vulnerability from cvelistv5 – Published: 2020-04-29 00:00 – Updated: 2024-08-04 10:03- CWE-91 - XML Injection (aka Blind XPath Injection)
| Vendor | Product | Version | |
|---|---|---|---|
| ABB | Central Licensing System |
Affected:
5.1 , < 5*
(custom)
|
|
| ABB | ABB Ability System 800xA |
Affected:
5.1
Affected: 6.0 Affected: 6.1 |
|
| ABB | Compact HMI |
Affected:
5.1
Affected: 6.0 |
|
| ABB | Control Builder Safe |
Affected:
1.0
Affected: 1.1 Affected: 2.0 |
|
| ABB | Symphony Plus S+ Operations |
Affected:
3 , ≤ 3.2
(custom)
|
|
| ABB | Symphony Plus S+ Engineering |
Affected:
1.1 , ≤ 2.2
(custom)
|
|
| ABB | Composer Harmony |
Affected:
5.1
Affected: 6.0 Affected: 6.1 |
|
| ABB | Composer Melody |
Affected:
5.3
Affected: 6 , ≤ 6.3 (custom) |
|
| ABB | Harmony OPC Server Standalone |
Affected:
6.0
Affected: 6.1 Affected: 7.0 |
|
| ABB | Advant OCS Control Builder A |
Affected:
1.3
Affected: 1.4 |
|
| ABB | Composer CTK |
Affected:
6.1
Affected: 6.2 |
|
| ABB | AdvaBuild |
Affected:
3.7 SP1
Affected: 3.7 SP2 |
|
| ABB | OPC Server for Mod 300 (non-800xA) |
Affected:
1.4
|
|
| ABB | OPC Data Link |
Affected:
2.1
Affected: 2.2 |
|
| ABB | Knowledge Manager |
Affected:
8.0
Affected: 9.0 Affected: 9.1 |
|
| ABB | Manufacturing Operations Management |
Affected:
1812
Affected: 1909 |
|
| ABB | Advant OCS AC 100 OPS Server |
Affected:
5.1
Affected: 6.0 Affected: 6.1 |
|
| ABB | ABB Ability™ SCADAvantage |
Affected:
5.1 , < unspecified
(custom)
Affected: unspecified , ≤ 5.6.5 (custom) |
{
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2024-08-04T10:03:44.804Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"tags": [
"x_transferred"
],
"url": "https://search.abb.com/library/Download.aspx?DocumentID=2PAA121231\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"tags": [
"x_transferred"
],
"url": "https://search.abb.com/library/Download.aspx?DocumentID=2PAA121230\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"tags": [
"x_transferred"
],
"url": "https://search.abb.com/library/Download.aspx?DocumentID=3CCA2020-003309\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"product": "Central Licensing System",
"vendor": "ABB",
"versions": [
{
"lessThan": "5*",
"status": "affected",
"version": "5.1",
"versionType": "custom"
}
]
},
{
"product": "ABB Ability System 800xA",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "5.1"
},
{
"status": "affected",
"version": "6.0"
},
{
"status": "affected",
"version": "6.1"
}
]
},
{
"product": "Compact HMI",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "5.1"
},
{
"status": "affected",
"version": "6.0"
}
]
},
{
"product": "Control Builder Safe",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "1.0"
},
{
"status": "affected",
"version": "1.1"
},
{
"status": "affected",
"version": "2.0"
}
]
},
{
"product": "Symphony Plus S+ Operations",
"vendor": "ABB",
"versions": [
{
"lessThanOrEqual": "3.2",
"status": "affected",
"version": "3",
"versionType": "custom"
}
]
},
{
"product": "Symphony Plus S+ Engineering",
"vendor": "ABB",
"versions": [
{
"lessThanOrEqual": "2.2",
"status": "affected",
"version": "1.1",
"versionType": "custom"
}
]
},
{
"product": "Composer Harmony",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "5.1"
},
{
"status": "affected",
"version": "6.0"
},
{
"status": "affected",
"version": "6.1"
}
]
},
{
"product": "Composer Melody",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "5.3"
},
{
"lessThanOrEqual": "6.3",
"status": "affected",
"version": "6",
"versionType": "custom"
}
]
},
{
"product": "Harmony OPC Server Standalone",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "6.0"
},
{
"status": "affected",
"version": "6.1"
},
{
"status": "affected",
"version": "7.0"
}
]
},
{
"product": "Advant OCS Control Builder A",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "1.3"
},
{
"status": "affected",
"version": "1.4"
}
]
},
{
"product": "Composer CTK",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "6.1"
},
{
"status": "affected",
"version": "6.2"
}
]
},
{
"product": "AdvaBuild",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "3.7 SP1"
},
{
"status": "affected",
"version": "3.7 SP2"
}
]
},
{
"product": "OPC Server for Mod 300 (non-800xA)",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "1.4"
}
]
},
{
"product": "OPC Data Link",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "2.1"
},
{
"status": "affected",
"version": "2.2"
}
]
},
{
"product": "Knowledge Manager",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "8.0"
},
{
"status": "affected",
"version": "9.0"
},
{
"status": "affected",
"version": "9.1"
}
]
},
{
"product": "Manufacturing Operations Management",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "1812"
},
{
"status": "affected",
"version": "1909"
}
]
},
{
"product": "Advant OCS AC 100 OPS Server",
"vendor": "ABB",
"versions": [
{
"status": "affected",
"version": "5.1"
},
{
"status": "affected",
"version": "6.0"
},
{
"status": "affected",
"version": "6.1"
}
]
},
{
"product": "ABB Ability\u2122 SCADAvantage",
"vendor": "ABB",
"versions": [
{
"lessThan": "unspecified",
"status": "affected",
"version": "5.1",
"versionType": "custom"
},
{
"lessThanOrEqual": "5.6.5",
"status": "affected",
"version": "unspecified",
"versionType": "custom"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "For the Central Licensing Server component used in ABB products ABB Ability\u2122 System 800xA and related system extensions versions 5.1, 6.0 and 6.1, Compact HMI versions 5.1 and 6.0, Control Builder Safe 1.0, 1.1 and 2.0, Symphony Plus -S+ Operations 3.0 to 3.2 Symphony Plus -S+ Engineering 1.1 to 2.2, Composer Harmony 5.1, 6.0 and 6.1, Melody Composer 5.3, 6.1/6.2 and SPE for Melody 1.0SPx (Composer 6.3), Harmony OPC Server (HAOPC) Standalone 6.0, 6.1 and 7.0, ABB Ability\u2122 System 800xA/ Advant\u00ae OCS Control Builder A 1.3 and 1.4, Advant\u00ae OCS AC100 OPC Server 5.1, 6.0 and 6.1, Composer CTK 6.1 and 6.2, AdvaBuild 3.7 SP1 and SP2, OPCServer for MOD 300 (non-800xA) 1.4, OPC Data Link 2.1 and 2.2, Knowledge Manager 8.0, 9.0 and 9.1, Manufacturing Operations Management 1812 and 1909, ABB AbilityTM SCADAvantage versions 5.1 to 5.6.5. an XML External Entity Injection vulnerability exists that allows an attacker to read or call arbitrary files from the license server and/or from the network and also block the license handling."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 9.4,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-91",
"description": "CWE-91 XML Injection (aka Blind XPath Injection)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2022-10-28T00:00:00.000Z",
"orgId": "2b718523-d88f-4f37-9bbd-300c20644bf9",
"shortName": "ABB"
},
"references": [
{
"url": "https://search.abb.com/library/Download.aspx?DocumentID=2PAA121231\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"url": "https://search.abb.com/library/Download.aspx?DocumentID=2PAA121230\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"url": "https://search.abb.com/library/Download.aspx?DocumentID=3CCA2020-003309\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "ABB Central Licensing System - XML External Entity Injection",
"x_generator": {
"engine": "Vulnogram 0.0.9"
}
}
},
"cveMetadata": {
"assignerOrgId": "2b718523-d88f-4f37-9bbd-300c20644bf9",
"assignerShortName": "ABB",
"cveId": "CVE-2020-8479",
"datePublished": "2020-04-29T00:00:00.000Z",
"dateReserved": "2020-01-30T00:00:00.000Z",
"dateUpdated": "2024-08-04T10:03:44.804Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
CVE-2019-17323 (GCVE-0-2019-17323)
Vulnerability from cvelistv5 – Published: 2019-10-30 20:49 – Updated: 2024-08-05 01:40- CWE-91 - XML Injection (aka Blind XPath Injection)
| URL | Tags |
|---|---|
| https://www.boho.or.kr/krcert/secNoticeView.do?bu… | x_refsource_MISC |
{
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2024-08-05T01:40:14.439Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://www.boho.or.kr/krcert/secNoticeView.do?bulletin_writing_sequence=35184"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"product": "REXPERT",
"vendor": "ClipSoft",
"versions": [
{
"status": "affected",
"version": "1.0.0.527 and earlier"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "ClipSoft REXPERT 1.0.0.527 and earlier version allows arbitrary file creation and execution via report print function of rexpert viewer with modified XML document. User interaction is required to exploit this vulnerability in that the target must visit a malicious web page."
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-91",
"description": "CWE-91: XML Injection (aka Blind XPath Injection)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2019-10-30T20:49:41.000Z",
"orgId": "cdd7a122-0fae-4202-8d86-14efbacc2863",
"shortName": "krcert"
},
"references": [
{
"tags": [
"x_refsource_MISC"
],
"url": "https://www.boho.or.kr/krcert/secNoticeView.do?bulletin_writing_sequence=35184"
}
],
"x_legacyV4Record": {
"CVE_data_meta": {
"ASSIGNER": "vuln@krcert.or.kr",
"ID": "CVE-2019-17323",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "REXPERT",
"version": {
"version_data": [
{
"version_value": "1.0.0.527 and earlier"
}
]
}
}
]
},
"vendor_name": "ClipSoft"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "ClipSoft REXPERT 1.0.0.527 and earlier version allows arbitrary file creation and execution via report print function of rexpert viewer with modified XML document. User interaction is required to exploit this vulnerability in that the target must visit a malicious web page."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "CWE-91: XML Injection (aka Blind XPath Injection)"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://www.boho.or.kr/krcert/secNoticeView.do?bulletin_writing_sequence=35184",
"refsource": "MISC",
"url": "https://www.boho.or.kr/krcert/secNoticeView.do?bulletin_writing_sequence=35184"
}
]
}
}
}
},
"cveMetadata": {
"assignerOrgId": "cdd7a122-0fae-4202-8d86-14efbacc2863",
"assignerShortName": "krcert",
"cveId": "CVE-2019-17323",
"datePublished": "2019-10-30T20:49:41.000Z",
"dateReserved": "2019-10-07T00:00:00.000Z",
"dateUpdated": "2024-08-05T01:40:14.439Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
GHSA-22J9-95FQ-2M3H
Vulnerability from github – Published: 2022-05-24 22:01 – Updated: 2024-04-04 03:07IBM Cognos Analytics 11.0 and 11.1 is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or cause the web server to make HTTP requests to arbitrary domains. IBM X-Force ID: 147369.
{
"affected": [],
"aliases": [
"CVE-2018-1721"
],
"database_specific": {
"cwe_ids": [
"CWE-91"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-11-09T02:15:00Z",
"severity": "HIGH"
},
"details": "IBM Cognos Analytics 11.0 and 11.1 is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or cause the web server to make HTTP requests to arbitrary domains. IBM X-Force ID: 147369.",
"id": "GHSA-22j9-95fq-2m3h",
"modified": "2024-04-04T03:07:34Z",
"published": "2022-05-24T22:01:06Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-1721"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/147369"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/1074144"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-2444-8GJ8-6FMX
Vulnerability from github – Published: 2023-03-27 21:30 – Updated: 2025-03-04 16:18Adobe Commerce versions 2.4.4-p2 (and earlier) and 2.4.5-p1 (and earlier) are affected by an XML Injection vulnerability that could lead to arbitrary file system read. An unauthenticated attacker can force the application to make arbitrary requests via injection of arbitrary URLs. Exploitation of this issue does not require user interaction.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "magento/community-edition"
},
"ranges": [
{
"events": [
{
"introduced": "2.4.5-p1"
},
{
"fixed": "2.4.5-p2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.4.5-p1"
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "magento/community-edition"
},
"versions": [
"2.4.5"
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "magento/community-edition"
},
"ranges": [
{
"events": [
{
"introduced": "2.4.4-p1"
},
{
"fixed": "2.4.4-p3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "magento/community-edition"
},
"versions": [
"2.4.4"
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "magento/project-community-edition"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "2.0.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-22247"
],
"database_specific": {
"cwe_ids": [
"CWE-91"
],
"github_reviewed": true,
"github_reviewed_at": "2025-03-04T16:18:00Z",
"nvd_published_at": "2023-03-27T21:15:00Z",
"severity": "HIGH"
},
"details": "Adobe Commerce versions 2.4.4-p2 (and earlier) and 2.4.5-p1 (and earlier) are affected by an XML Injection vulnerability that could lead to arbitrary file system read. An unauthenticated attacker can force the application to make arbitrary requests via injection of arbitrary URLs. Exploitation of this issue does not require user interaction.",
"id": "GHSA-2444-8gj8-6fmx",
"modified": "2025-03-04T16:18:00Z",
"published": "2023-03-27T21:30:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-22247"
},
{
"type": "PACKAGE",
"url": "https://github.com/magento/magento2"
},
{
"type": "WEB",
"url": "https://helpx.adobe.com/security/products/magento/apsb23-17.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Magento Open Source allows XML Injection"
}
GHSA-26RR-V2J2-25FH
Vulnerability from github – Published: 2021-08-30 17:20 – Updated: 2021-08-30 16:42Impact
Layout XML enabled admin users to execute arbitrary commands via block methods.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "openmage/magento-lts"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "19.4.15"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "openmage/magento-lts"
},
"ranges": [
{
"events": [
{
"introduced": "20.0.0"
},
{
"fixed": "20.0.13"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-32758"
],
"database_specific": {
"cwe_ids": [
"CWE-91"
],
"github_reviewed": true,
"github_reviewed_at": "2021-08-30T16:42:41Z",
"nvd_published_at": "2021-08-27T18:15:00Z",
"severity": "HIGH"
},
"details": "### Impact\nLayout XML enabled admin users to execute arbitrary commands via block methods.",
"id": "GHSA-26rr-v2j2-25fh",
"modified": "2021-08-30T16:42:41Z",
"published": "2021-08-30T17:20:52Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/OpenMage/magento-lts/security/advisories/GHSA-26rr-v2j2-25fh"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-32758"
},
{
"type": "WEB",
"url": "https://github.com/OpenMage/magento-lts/commit/b99307d00b59c4a226a1e3e4083f02cf2fc8fce7"
},
{
"type": "WEB",
"url": "https://github.com/OpenMage/magento-lts/releases/tag/v19.4.15"
},
{
"type": "WEB",
"url": "https://github.com/OpenMage/magento-lts/releases/tag/v20.0.13"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Layout XML Arbitrary Code Fix "
}
GHSA-27P8-2357-5QQV
Vulnerability from github – Published: 2026-09-08 21:02 – Updated: 2026-09-08 21:02Summary
The @xmldom/xmldom serializer emits DocumentType.name verbatim into the
<!DOCTYPE …> declaration with no well-formedness guard. GHSA-f6ww-3ggp-fr8h
(CVE-2026-41674) hardened the serializer's requireWellFormed path for a
DocumentType's sibling fields — publicId, systemId, and internalSubset —
but it did not add any check for name. A > (or whitespace) in the name
terminates the doctype declaration early, letting the remaining characters
become sibling markup in the serialized output.
Because requireWellFormed: true — the recommended mitigation for the prior
xmldom injection CVEs — performs no validation on the DocType name, this is a
bypass of that control, in the same family as the open element-name
(GHSA-w2rr-34g9-rvrj) and attribute-name (GHSA-4w3w-2rp5-g8jm) name-injection advisories.
Details
The serializer's DOCUMENT_TYPE_NODE case runs the requireWellFormed block
only against publicId, systemId, and internalSubset, then pushes
n.name directly into the buffer between the <!DOCTYPE prefix and the
closing >:
- 0.9.x (v0.9.10,
bb7a085): serializer DocType case,lib/dom.js#L3256-L3283— therequireWellFormedblock (#L3259-L3269) validatespublicId/systemId/internalSubsetbut notname, which is emitted verbatim at #L3270. - 0.8.x (v0.8.13,
e5c1480): serializer DocType case,lib/dom.js#L1914-L1946— same structure;nameis emitted verbatim at #L1928. - unscoped
xmldom(v0.6.0,c80a161):lib/dom.js#L1105emitsnode.nameverbatim; this line predatesrequireWellFormed, so there is no well-formedness path at all.
Enabling write paths
DocumentType.name is a plain, writable own-property, so the enabling vector
differs by line:
- 0.9.x —
createDocumentType()validates the name viavalidateQualifiedName(lib/dom.js#L925-L936, validation at #L926), so the deliverable vector is a direct property write (dt.name = 'html><script>…') to the unguarded own-property. - 0.8.x —
createDocumentType()does not validate the name (lib/dom.js#L456-L464), so the malicious name is reachable directly throughcreateDocumentType()as well as via direct property write. - unscoped
xmldom(<= 0.6.0) —createDocumentType()does not validate the name (lib/dom.js#L286), same as 0.8.x.
This is the same structural root cause the sibling name-injection advisories
share: the serializer's requireWellFormed path validates content delimiters
but no name field, and every name-like field is a plain writable property, so
mutation / direct property-write bypasses any creation-time check.
Root Cause
- The serializer's
requireWellFormedDocType block checkspublicId,systemId, andinternalSubset(the fields hardened by GHSA-f6ww-3ggp-fr8h) but has no check forname. DocumentType.nameis a plain writable own-property; on 0.8.x and the unscoped packagecreateDocumentType()does not validate it either.- The serializer emits
namedirectly between the doctype delimiters:<!DOCTYPE ${name}…>.
Proof of Concept
Run against @xmldom/xmldom v0.9.10 (commit bb7a085):
const { DOMImplementation, XMLSerializer, DOMParser } = require('@xmldom/xmldom');
const impl = new DOMImplementation();
const serializer = new XMLSerializer();
// 0.9.x createDocumentType validates the name, so overwrite it via direct property write
const dt = impl.createDocumentType('html', '', '');
dt.name = 'html><script xmlns="http://www.w3.org/1999/xhtml">alert(1)</script';
const doc = impl.createDocument(null, 'r', dt);
const output = serializer.serializeToString(doc, { requireWellFormed: true });
console.log(output);
// Output: <!DOCTYPE html><script xmlns="http://www.w3.org/1999/xhtml">alert(1)</script><r/>
//
// requireWellFormed: true did NOT prevent the injection (no exception thrown).
// The injected <script> is well-formed XHTML that a browser would execute.
Confirmed runtime behavior:
- 0.9.x —
createDocumentType()rejects the malicious name at creation (InvalidCharacterError); a direct write todt.namebypasses that, andserializeToString(…, { requireWellFormed: true })emits the breakout with no exception. - Re-parse confirmation — re-parsing the output shows the injected
<script>is a real second top-level element originating entirely from the DocType name: the parser rejects it withHierarchyRequestError: Only one element can be added and only after doctype. A comment-injection variant (dt.name = 'html><!--INJECTED--', output<!DOCTYPE html><!--INJECTED--><r/>) re-parses cleanly and the injected comment node is enumerable, confirming the injected node is structurally live. - 0.8.x (v0.8.13,
e5c1480) —createDocumentType('html><script>…', '', '')accepts the malicious name directly (no creation-time validation), andserializeToString(doc, null, null, { requireWellFormed: true })produces<!DOCTYPE html><script>alert(1)</script><r/>with no exception.
A browser reproduction does not apply: browsers keep DocumentType.name
readonly, so the direct-write vector cannot be reproduced in a browser DOM.
The injection is specific to xmldom exposing name as writable and serializing
it without a guard.
Impact
Applications that build a DocumentType node with an attacker-influenced
name — via direct property write on any affected line, or via
createDocumentType() on 0.8.x and the unscoped package — and serialize the
document are vulnerable to XML/markup injection:
- XML structure injection — breaking out of the
<!DOCTYPE …>declaration to inject arbitrary sibling elements, comments, or additional markup into the output. - XSS via XHTML — if the serialized output is served as XHTML or processed
by a browser-based XML parser, an injected
<script>element (in the XHTML namespace) executes. - requireWellFormed bypass — applications that adopted
requireWellFormed: trueas a mitigation for the prior injection CVEs (including the sibling DocType fields fixed by GHSA-f6ww-3ggp-fr8h) remain vulnerable through the DocTypename.
Fix Applied
Under requireWellFormed, the serializer validates the DocType name as a well-formed XML
Name and throws InvalidStateError when it is not — matching the sibling
publicId/systemId/internalSubset checks. Non-breaking and opt-in; ships on both maintained versions. No
creation-time change is made: 0.9.x already validates the name at createDocumentType, and the
0.8.x/unscoped creation gap cannot be closed without a breaking change, so it is left
unfixed. See the XML Name production.
⚠ Opt-in required. Protection is not automatic. Existing serialization calls remain vulnerable unless
{ requireWellFormed: true }is explicitly passed. Applications that serialize untrusted DOM content should audit allserializeToString()call sites and add it.
Proof of Concept - fixed path
const { DOMImplementation, XMLSerializer } = require('@xmldom/xmldom');
const impl = new DOMImplementation();
const serializer = new XMLSerializer();
const dt = impl.createDocumentType('html', '', '');
dt.name = 'html><script xmlns="http://www.w3.org/1999/xhtml">alert(1)</script';
const doc = impl.createDocument(null, 'r', dt);
// Default path: the ill-formed name is still emitted verbatim (injection present).
console.log(serializer.serializeToString(doc));
// <!DOCTYPE html><script xmlns="http://www.w3.org/1999/xhtml">alert(1)</script><r/>
// Opt-in path: serialization throws instead of emitting the breakout.
serializer.serializeToString(doc, { requireWellFormed: true });
// throws InvalidStateError
Why the default stays verbatim
W3C DOM Parsing's require-well-formed flag defaults to false, and the browser
XMLSerializer emits the name verbatim in that default mode. Unconditionally
throwing would be an unjustified breaking change against that specified default,
so the guard is opt-in behind { requireWellFormed: true }.
Residual limitation
The default serialization path still emits the ill-formed DocType name
verbatim; protection applies only when requireWellFormed: true is passed. No
creation-time validation is added for the DocType name: 0.9.x already validates
at createDocumentType, and the 0.8.x/unscoped creation gap is left unfixed — it
cannot be closed without a breaking change.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.8.14"
},
"package": {
"ecosystem": "npm",
"name": "@xmldom/xmldom"
},
"ranges": [
{
"events": [
{
"introduced": "0.7.0"
},
{
"fixed": "0.8.15"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.9.11"
},
"package": {
"ecosystem": "npm",
"name": "@xmldom/xmldom"
},
"ranges": [
{
"events": [
{
"introduced": "0.9.0"
},
{
"fixed": "0.9.12"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "xmldom"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.6.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-83608"
],
"database_specific": {
"cwe_ids": [
"CWE-91"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-08T21:02:51Z",
"nvd_published_at": "2026-09-01T15:17:38Z",
"severity": "HIGH"
},
"details": "## Summary\n\nThe `@xmldom/xmldom` serializer emits `DocumentType.name` verbatim into the\n`\u003c!DOCTYPE \u2026\u003e` declaration with no well-formedness guard. GHSA-f6ww-3ggp-fr8h\n(CVE-2026-41674) hardened the serializer\u0027s `requireWellFormed` path for a\nDocumentType\u0027s sibling fields \u2014 `publicId`, `systemId`, and `internalSubset` \u2014\nbut it did **not** add any check for `name`. A `\u003e` (or whitespace) in the name\nterminates the doctype declaration early, letting the remaining characters\nbecome sibling markup in the serialized output.\n\nBecause `requireWellFormed: true` \u2014 the recommended mitigation for the prior\nxmldom injection CVEs \u2014 performs no validation on the DocType `name`, this is a\nbypass of that control, in the same family as the open element-name\n(GHSA-w2rr-34g9-rvrj) and attribute-name (GHSA-4w3w-2rp5-g8jm) name-injection advisories.\n\n## Details\n\nThe serializer\u0027s `DOCUMENT_TYPE_NODE` case runs the `requireWellFormed` block\nonly against `publicId`, `systemId`, and `internalSubset`, then pushes\n`n.name` directly into the buffer between the `\u003c!DOCTYPE ` prefix and the\nclosing `\u003e`:\n\n- 0.9.x (v0.9.10, `bb7a085`):\n [serializer DocType case, `lib/dom.js#L3256-L3283`](https://github.com/xmldom/xmldom/blob/bb7a085dc5ba1eea3212388509b97bb4b4af32b9/lib/dom.js#L3256-L3283)\n \u2014 the `requireWellFormed` block ([#L3259-L3269](https://github.com/xmldom/xmldom/blob/bb7a085dc5ba1eea3212388509b97bb4b4af32b9/lib/dom.js#L3259-L3269))\n validates `publicId`/`systemId`/`internalSubset` but not `name`, which is\n emitted verbatim at [#L3270](https://github.com/xmldom/xmldom/blob/bb7a085dc5ba1eea3212388509b97bb4b4af32b9/lib/dom.js#L3270).\n- 0.8.x (v0.8.13, `e5c1480`):\n [serializer DocType case, `lib/dom.js#L1914-L1946`](https://github.com/xmldom/xmldom/blob/e5c14802592685bb872c042c54c3f73758875c85/lib/dom.js#L1914-L1946)\n \u2014 same structure; `name` is emitted verbatim at [#L1928](https://github.com/xmldom/xmldom/blob/e5c14802592685bb872c042c54c3f73758875c85/lib/dom.js#L1928).\n- unscoped `xmldom` (v0.6.0, `c80a161`):\n [`lib/dom.js#L1105`](https://github.com/xmldom/xmldom/blob/c80a161172cc4d8733583bf0cf59abfa589f6d9e/lib/dom.js#L1105)\n emits `node.name` verbatim; this line predates `requireWellFormed`, so there\n is no well-formedness path at all.\n\n### Enabling write paths\n\n`DocumentType.name` is a plain, writable own-property, so the enabling vector\ndiffers by line:\n\n- **0.9.x** \u2014 `createDocumentType()` validates the name via\n `validateQualifiedName` ([`lib/dom.js#L925-L936`](https://github.com/xmldom/xmldom/blob/bb7a085dc5ba1eea3212388509b97bb4b4af32b9/lib/dom.js#L925-L936),\n validation at [#L926](https://github.com/xmldom/xmldom/blob/bb7a085dc5ba1eea3212388509b97bb4b4af32b9/lib/dom.js#L926)),\n so the deliverable vector is a **direct property write**\n (`dt.name = \u0027html\u003e\u003cscript\u003e\u2026\u0027`) to the unguarded own-property.\n- **0.8.x** \u2014 `createDocumentType()` does **not** validate the name\n ([`lib/dom.js#L456-L464`](https://github.com/xmldom/xmldom/blob/e5c14802592685bb872c042c54c3f73758875c85/lib/dom.js#L456-L464)),\n so the malicious name is reachable directly through `createDocumentType()` as\n well as via direct property write.\n- **unscoped `xmldom` (\u003c= 0.6.0)** \u2014 `createDocumentType()` does not validate\n the name ([`lib/dom.js#L286`](https://github.com/xmldom/xmldom/blob/c80a161172cc4d8733583bf0cf59abfa589f6d9e/lib/dom.js#L286)),\n same as 0.8.x.\n\nThis is the same structural root cause the sibling name-injection advisories\nshare: the serializer\u0027s `requireWellFormed` path validates content delimiters\nbut no name field, and every name-like field is a plain writable property, so\nmutation / direct property-write bypasses any creation-time check.\n\n### Root Cause\n\n1. The serializer\u0027s `requireWellFormed` DocType block checks `publicId`,\n `systemId`, and `internalSubset` (the fields hardened by GHSA-f6ww-3ggp-fr8h)\n but has no check for `name`.\n2. `DocumentType.name` is a plain writable own-property; on 0.8.x and the\n unscoped package `createDocumentType()` does not validate it either.\n3. The serializer emits `name` directly between the doctype delimiters:\n `\u003c!DOCTYPE ${name}\u2026\u003e`.\n\n## Proof of Concept\n\nRun against `@xmldom/xmldom` v0.9.10 (commit `bb7a085`):\n\n```javascript\nconst { DOMImplementation, XMLSerializer, DOMParser } = require(\u0027@xmldom/xmldom\u0027);\n\nconst impl = new DOMImplementation();\nconst serializer = new XMLSerializer();\n\n// 0.9.x createDocumentType validates the name, so overwrite it via direct property write\nconst dt = impl.createDocumentType(\u0027html\u0027, \u0027\u0027, \u0027\u0027);\ndt.name = \u0027html\u003e\u003cscript xmlns=\"http://www.w3.org/1999/xhtml\"\u003ealert(1)\u003c/script\u0027;\nconst doc = impl.createDocument(null, \u0027r\u0027, dt);\n\nconst output = serializer.serializeToString(doc, { requireWellFormed: true });\nconsole.log(output);\n// Output: \u003c!DOCTYPE html\u003e\u003cscript xmlns=\"http://www.w3.org/1999/xhtml\"\u003ealert(1)\u003c/script\u003e\u003cr/\u003e\n//\n// requireWellFormed: true did NOT prevent the injection (no exception thrown).\n// The injected \u003cscript\u003e is well-formed XHTML that a browser would execute.\n```\n\nConfirmed runtime behavior:\n\n- **0.9.x** \u2014 `createDocumentType()` rejects the malicious name at creation\n (`InvalidCharacterError`); a direct write to `dt.name` bypasses that, and\n `serializeToString(\u2026, { requireWellFormed: true })` emits the breakout with no\n exception.\n- **Re-parse confirmation** \u2014 re-parsing the output shows the injected\n `\u003cscript\u003e` is a real second top-level element originating entirely from the\n DocType name: the parser rejects it with\n `HierarchyRequestError: Only one element can be added and only after doctype`.\n A comment-injection variant (`dt.name = \u0027html\u003e\u003c!--INJECTED--\u0027`, output\n `\u003c!DOCTYPE html\u003e\u003c!--INJECTED--\u003e\u003cr/\u003e`) re-parses cleanly and the injected\n comment node is enumerable, confirming the injected node is structurally live.\n- **0.8.x** (v0.8.13, `e5c1480`) \u2014 `createDocumentType(\u0027html\u003e\u003cscript\u003e\u2026\u0027, \u0027\u0027, \u0027\u0027)`\n accepts the malicious name directly (no creation-time validation), and\n `serializeToString(doc, null, null, { requireWellFormed: true })` produces\n `\u003c!DOCTYPE html\u003e\u003cscript\u003ealert(1)\u003c/script\u003e\u003cr/\u003e` with no exception.\n\nA browser reproduction does not apply: browsers keep `DocumentType.name`\n`readonly`, so the direct-write vector cannot be reproduced in a browser DOM.\nThe injection is specific to xmldom exposing `name` as writable and serializing\nit without a guard.\n\n## Impact\n\nApplications that build a `DocumentType` node with an attacker-influenced\n`name` \u2014 via direct property write on any affected line, or via\n`createDocumentType()` on 0.8.x and the unscoped package \u2014 and serialize the\ndocument are vulnerable to XML/markup injection:\n\n- **XML structure injection** \u2014 breaking out of the `\u003c!DOCTYPE \u2026\u003e` declaration\n to inject arbitrary sibling elements, comments, or additional markup into the\n output.\n- **XSS via XHTML** \u2014 if the serialized output is served as XHTML or processed\n by a browser-based XML parser, an injected `\u003cscript\u003e` element (in the XHTML\n namespace) executes.\n- **requireWellFormed bypass** \u2014 applications that adopted\n `requireWellFormed: true` as a mitigation for the prior injection CVEs\n (including the sibling DocType fields fixed by GHSA-f6ww-3ggp-fr8h) remain\n vulnerable through the DocType `name`.\n\n## Fix Applied\n\nUnder `requireWellFormed`, the serializer validates the DocType `name` as a well-formed XML\n`Name` and throws `InvalidStateError` when it is not \u2014 matching the sibling\n`publicId`/`systemId`/`internalSubset` checks. Non-breaking and opt-in; ships on both maintained versions. No\ncreation-time change is made: 0.9.x already validates the name at `createDocumentType`, and the\n0.8.x/unscoped creation gap cannot be closed without a breaking change, so it is left\nunfixed. See the [XML `Name` production](https://www.w3.org/TR/xml/#NT-Name).\n\u003e **\u26a0 Opt-in required.** Protection is not automatic. Existing serialization calls remain\n\u003e vulnerable unless `{ requireWellFormed: true }` is explicitly passed. Applications that\n\u003e serialize untrusted DOM content should audit all `serializeToString()` call sites and add it.\n\n### Proof of Concept - fixed path\n\n```javascript\nconst { DOMImplementation, XMLSerializer } = require(\u0027@xmldom/xmldom\u0027);\n\nconst impl = new DOMImplementation();\nconst serializer = new XMLSerializer();\n\nconst dt = impl.createDocumentType(\u0027html\u0027, \u0027\u0027, \u0027\u0027);\ndt.name = \u0027html\u003e\u003cscript xmlns=\"http://www.w3.org/1999/xhtml\"\u003ealert(1)\u003c/script\u0027;\nconst doc = impl.createDocument(null, \u0027r\u0027, dt);\n\n// Default path: the ill-formed name is still emitted verbatim (injection present).\nconsole.log(serializer.serializeToString(doc));\n// \u003c!DOCTYPE html\u003e\u003cscript xmlns=\"http://www.w3.org/1999/xhtml\"\u003ealert(1)\u003c/script\u003e\u003cr/\u003e\n\n// Opt-in path: serialization throws instead of emitting the breakout.\nserializer.serializeToString(doc, { requireWellFormed: true });\n// throws InvalidStateError\n```\n\n### Why the default stays verbatim\n\nW3C DOM Parsing\u0027s require-well-formed flag defaults to false, and the browser\n`XMLSerializer` emits the name verbatim in that default mode. Unconditionally\nthrowing would be an unjustified breaking change against that specified default,\nso the guard is opt-in behind `{ requireWellFormed: true }`.\n\n### Residual limitation\n\nThe default serialization path still emits the ill-formed DocType `name`\nverbatim; protection applies only when `requireWellFormed: true` is passed. No\ncreation-time validation is added for the DocType `name`: 0.9.x already validates\nat `createDocumentType`, and the 0.8.x/unscoped creation gap is left unfixed \u2014 it\ncannot be closed without a breaking change.",
"id": "GHSA-27p8-2357-5qqv",
"modified": "2026-09-08T21:02:51Z",
"published": "2026-09-08T21:02:51Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/xmldom/xmldom/security/advisories/GHSA-27p8-2357-5qqv"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-83608"
},
{
"type": "WEB",
"url": "https://github.com/xmldom/xmldom/pull/1071"
},
{
"type": "WEB",
"url": "https://github.com/xmldom/xmldom/pull/1072"
},
{
"type": "WEB",
"url": "https://github.com/xmldom/xmldom/commit/57aec90ac57b4408ae7c5d1746bf2a693b5ed90e"
},
{
"type": "WEB",
"url": "https://github.com/xmldom/xmldom/commit/85f12eb4d14b44de33216cfb72b50af4d24e9fdd"
},
{
"type": "PACKAGE",
"url": "https://github.com/xmldom/xmldom"
},
{
"type": "WEB",
"url": "https://github.com/xmldom/xmldom/releases/tag/0.8.15"
},
{
"type": "WEB",
"url": "https://github.com/xmldom/xmldom/releases/tag/0.9.12"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "xmldom: DocType `name` Injection Bypasses requireWellFormed"
}
GHSA-2894-36C8-F98V
Vulnerability from github – Published: 2022-05-19 00:00 – Updated: 2022-05-28 00:00The Zoom Client for Meetings (for Android, iOS, Linux, MacOS, and Windows) before version 5.10.0 failed to properly parse XML stanzas in XMPP messages. This can allow a malicious user to break out of the current XMPP message context and create a new message context to have the receiving users client perform a variety of actions.This issue could be used in a more sophisticated attack to forge XMPP messages from the server.
{
"affected": [],
"aliases": [
"CVE-2022-22784"
],
"database_specific": {
"cwe_ids": [
"CWE-91"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-05-18T16:15:00Z",
"severity": "HIGH"
},
"details": "The Zoom Client for Meetings (for Android, iOS, Linux, MacOS, and Windows) before version 5.10.0 failed to properly parse XML stanzas in XMPP messages. This can allow a malicious user to break out of the current XMPP message context and create a new message context to have the receiving users client perform a variety of actions.This issue could be used in a more sophisticated attack to forge XMPP messages from the server.",
"id": "GHSA-2894-36c8-f98v",
"modified": "2022-05-28T00:00:27Z",
"published": "2022-05-19T00:00:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-22784"
},
{
"type": "WEB",
"url": "https://explore.zoom.us/en/trust/security/security-bulletin"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-2G98-F9JV-W8C5
Vulnerability from github – Published: 2024-05-20 18:06 – Updated: 2024-05-20 18:06A vulnerability has been identified in the robrichards/xmlseclibs library, specifically related to XPath injection. The issue arises from inadequate filtering of user input before it is incorporated into XPath expressions.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "robrichards/xmlseclibs"
},
"ranges": [
{
"events": [
{
"introduced": "1.0.0"
},
{
"fixed": "3.0.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-91"
],
"github_reviewed": true,
"github_reviewed_at": "2024-05-20T18:06:52Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "A vulnerability has been identified in the robrichards/xmlseclibs library, specifically related to XPath injection. The issue arises from inadequate filtering of user input before it is incorporated into XPath expressions.",
"id": "GHSA-2g98-f9jv-w8c5",
"modified": "2024-05-20T18:06:52Z",
"published": "2024-05-20T18:06:52Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/robrichards/xmlseclibs/commit/649032643f7aac493e91ca318da0339aec72aa4a"
},
{
"type": "WEB",
"url": "https://github.com/FriendsOfPHP/security-advisories/blob/master/robrichards/xmlseclibs/2018-09-27.yaml"
},
{
"type": "PACKAGE",
"url": "https://github.com/robrichards/xmlseclibs"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "robrichards/xmlseclibs XPath injection"
}
GHSA-2H59-FHPR-VFX4
Vulnerability from github – Published: 2023-09-27 15:30 – Updated: 2024-04-04 07:54A remote code execution (RCE) vulnerability in the xmlrpc.php endpoint of NodeBB Inc NodeBB forum software prior to v1.18.6 allows attackers to execute arbitrary code via crafted XML-RPC requests.
{
"affected": [],
"aliases": [
"CVE-2023-43187"
],
"database_specific": {
"cwe_ids": [
"CWE-91"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-09-27T15:19:33Z",
"severity": "CRITICAL"
},
"details": "A remote code execution (RCE) vulnerability in the xmlrpc.php endpoint of NodeBB Inc NodeBB forum software prior to v1.18.6 allows attackers to execute arbitrary code via crafted XML-RPC requests.",
"id": "GHSA-2h59-fhpr-vfx4",
"modified": "2024-04-04T07:54:35Z",
"published": "2023-09-27T15:30:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-43187"
},
{
"type": "WEB",
"url": "https://github.com/jagat-singh-chaudhary/CVE/blob/main/CVE-2023-43187"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-2HJG-246P-2F5P
Vulnerability from github – Published: 2022-03-11 00:02 – Updated: 2024-09-18 21:30An issue was discovered in OverIT Geocall before 8.0. An authenticated user who has the Test Trasformazione XSL functionality enabled can exploit a XSLT Injection vulnerability. Attackers could exploit this issue to achieve remote code execution.
{
"affected": [],
"aliases": [
"CVE-2022-22834"
],
"database_specific": {
"cwe_ids": [
"CWE-91"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-03-10T17:45:00Z",
"severity": "HIGH"
},
"details": "An issue was discovered in OverIT Geocall before 8.0. An authenticated user who has the Test Trasformazione XSL functionality enabled can exploit a XSLT Injection vulnerability. Attackers could exploit this issue to achieve remote code execution.",
"id": "GHSA-2hjg-246p-2f5p",
"modified": "2024-09-18T21:30:37Z",
"published": "2022-03-11T00:02:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-22834"
},
{
"type": "WEB",
"url": "https://labs.yarix.com/2022/03/overit-framework-xslt-injection-and-xxe-cve-2022-22834-cve-2022-22835"
},
{
"type": "WEB",
"url": "https://labs.yarix.com/advisories/cve-2022-22834"
},
{
"type": "WEB",
"url": "https://overit.us/products/geocall"
},
{
"type": "WEB",
"url": "https://www.overit.ai/product/nextgen-fsm"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation MIT-5
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
CAPEC-250: XML Injection
An attacker utilizes crafted XML user-controllable input to probe, attack, and inject data into the XML database, using techniques similar to SQL injection. The user-controllable input can allow for unauthorized viewing of data, bypassing authentication or the front-end application for direct XML database access, and possibly altering database information.
CAPEC-83: XPath Injection
An attacker can craft special user-controllable input consisting of XPath expressions to inject the XML database and bypass authentication or glean information that they normally would not be able to. XPath Injection enables an attacker to talk directly to the XML database, thus bypassing the application completely. XPath Injection results from the failure of an application to properly sanitize input used as part of dynamic XPath expressions used to query an XML database.