LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19904: Persistent XSS exists in XSLT CMS via the create/?action=items.edit&type=Page "body" field.

Persistent XSS exists in XSLT CMS via the create/?action=items.edit&type=Page "body" field.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-19904 is a stored cross-site scripting issue reported in XSLT CMS. If exploitable, malicious content saved in a page body could run in another user’s browser when viewed. The business risk is account misuse, content tampering, or session exposure, but the sources do not identify affected versions or a vendor fix.

Executive priority

Treat as a moderate web application risk. Prioritize if XSLT CMS is internet-facing, supports public or broad content editing, or is used by privileged staff. Lack of version and fix detail means teams should verify exposure before urgent remediation work.

Technical view

The CVE describes persistent XSS in XSLT CMS through the Page editor body field at create/?action=items.edit&type=Page. It is classified as CWE-79 with CVSS 3.1 score 6.1: network reachable, low complexity, no privileges required, user interaction required, changed scope, low confidentiality and integrity impact.

Likely exposure

Exposure is most likely where XSLT CMS is deployed and untrusted or weakly controlled users can create or edit Page body content. The source bundle does not provide vendor, product version, CPE, deployment prevalence, or patch information.

Exploitation context

The provided data does not show CISA KEV listing or any cited confirmation of active exploitation. The vulnerability requires a victim to view affected stored content, so impact depends on who can edit pages and who later views them.

Researcher notes

Evidence is sparse: the CVE description, CVSS vector, CWE-79 classification, and one external PDF reference. The official affected product metadata is n/a, so do not infer specific versions or forks without independent confirmation.

Mitigation direction

  • Inventory any XSLT CMS deployments and confirm whether Page body editing is enabled.
  • Check upstream or vendor guidance for fixed releases or official mitigations.
  • Restrict page editing to trusted users until exposure is understood.
  • Ensure stored page body content is sanitized and encoded before rendering.
  • Review existing page content for unexpected active markup or suspicious edits.

Validation and detection

  • Confirm whether the application is XSLT CMS and matches the vulnerable page-editing workflow.
  • Identify who can access the Page body editor and whether anonymous editing is possible.
  • In a controlled environment, verify saved body content is safely encoded when rendered.
  • Review CMS content history and web logs for suspicious page updates.
  • Document compensating controls such as editor restrictions and output encoding.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookup
cve · low confidence lookup

CVE-2018-19904 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2018-19904Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.