FKIE_CVE-2022-34323
Vulnerability from fkie_nvd - Published: 2023-01-01 08:15 - Updated: 2026-06-17 04:505.4 (Medium) - CVSS:3.1/
| URL | Tags | ||
|---|---|---|---|
| cve@mitre.org | https://www.synacktiv.com/sites/default/files/2022-12/sage_xrt_multiple_xss.pdf | Exploit, Technical Description, Third Party Advisory | |
| af854a3a-2127-422b-91ae-364da2661108 | https://www.synacktiv.com/sites/default/files/2022-12/sage_xrt_multiple_xss.pdf | Exploit, Technical Description, Third Party Advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| sage | sage_xrt_business_exchange | 12.4.302 |
{
"affected": [
{
"affectedData": [
{
"product": "n/a",
"vendor": "n/a",
"versions": [
{
"status": "affected",
"version": "n/a"
}
]
}
],
"source": "cve@mitre.org"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:sage:sage_xrt_business_exchange:12.4.302:*:*:*:*:*:*:*",
"matchCriteriaId": "1CD3D3D4-3872-4DBB-9355-43874D764788",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Multiple XSS issues were discovered in Sage XRT Business Exchange 12.4.302 that allow an attacker to execute JavaScript code in the context of other users\u0027 browsers. The attacker needs to be authenticated to reach the vulnerable features. An issue is present in the Filters and Display model features (OnlineBanking \u003e Web Monitoring \u003e Settings \u003e Filters / Display models). The name of a filter or a display model is interpreted as HTML and can thus embed JavaScript code, which is executed when displayed. This is a stored XSS. Another issue is present in the Notification feature (OnlineBanking \u003e Configuration \u003e Notifications and alerts \u003e Alerts *). The name of an alert is interpreted as HTML, and can thus embed JavaScript code, which is executed when displayed. This is a stored XSS. (Also, an issue is present in the File download feature, accessible via /OnlineBanking/cgi/isapi.dll/DOWNLOADFRS. When requesting to show the list of downloadable files, the contents of three form fields are embedded in the JavaScript code without prior sanitization. This is essentially a self-XSS.)"
},
{
"lang": "es",
"value": "Se descubrieron m\u00faltiples problemas XSS en Sage XRT Business Exchange 12.4.302 que permiten a un atacante ejecutar c\u00f3digo JavaScript en el contexto de los navegadores de otros usuarios. El atacante debe autenticarse para acceder a las funciones vulnerables. Hay un problema presente en las funciones del modelo Filtros y Visualizaci\u00f3n (Banca en l\u00ednea \u0026gt; Monitoreo web \u0026gt; Configuraci\u00f3n \u0026gt; Filtros / Modelos de visualizaci\u00f3n). El nombre de un filtro o de un modelo de visualizaci\u00f3n se interpreta como HTML y, por lo tanto, puede incrustar c\u00f3digo JavaScript, que se ejecuta cuando se muestra. Este es un XSS almacenado. Otro problema est\u00e1 presente en la funci\u00f3n de Notificaciones (Banca en L\u00ednea \u0026gt; Configuraci\u00f3n \u0026gt; Notificaciones y alertas \u0026gt; Alertas *). El nombre de una alerta se interpreta como HTML y, por lo tanto, puede incrustar c\u00f3digo JavaScript, que se ejecuta cuando se muestra. Este es un XSS almacenado. (Adem\u00e1s, existe un problema en la funci\u00f3n de descarga de archivos, a la que se puede acceder a trav\u00e9s de /OnlineBanking/cgi/isapi.dll/DOWNLOADFRS. Cuando se solicita mostrar la lista de archivos descargables, el contenido de tres campos del formulario se incrusta en el c\u00f3digo JavaScript sin previo aviso. sanitizaci\u00f3n. Esto es esencialmente un auto-XSS.)"
}
],
"id": "CVE-2022-34323",
"lastModified": "2026-06-17T04:50:07.020",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2022-34323",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-04-11T14:07:17.218185Z",
"version": "2.0.3"
}
}
]
},
"published": "2023-01-01T08:15:10.157",
"references": [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Technical Description",
"Third Party Advisory"
],
"url": "https://www.synacktiv.com/sites/default/files/2022-12/sage_xrt_multiple_xss.pdf"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Technical Description",
"Third Party Advisory"
],
"url": "https://www.synacktiv.com/sites/default/files/2022-12/sage_xrt_multiple_xss.pdf"
}
],
"sourceIdentifier": "cve@mitre.org",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-79"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-79"
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.