LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10726: A stored XSS vulnerability was found in Datenstrom Yellow 0.7.3 via an "Edit page" action.

A stored XSS vulnerability was found in Datenstrom Yellow 0.7.3 via an "Edit page" action. NOTE: the vendor disputes the relevance of this report because an installation accessible to untrusted users is supposed to have parserSafeMode=1 in system/config/config.ini to prevent XSS

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-10726 is a reported stored cross-site scripting issue in Datenstrom Yellow 0.7.3 through page editing. Business risk is limited by required edit privileges and victim interaction, but untrusted editors could potentially place script content that affects later viewers. The vendor disputes relevance when untrusted-accessible installs use parserSafeMode=1.

Executive priority

Treat as a moderate configuration-sensitive web application risk. Prioritize review if Yellow editing is exposed to customers, partners, contractors, or other low-trust users. If editing is limited to trusted administrators and parserSafeMode is enabled, urgency is lower.

Technical view

The CVE describes CWE-79 stored XSS via the Yellow 0.7.3 "Edit page" action. CVSS 3.1 is 5.4: network reachable, low complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact. Published affected CPE data is not provided.

Likely exposure

Most relevant exposure is a Datenstrom Yellow 0.7.3 site where page editing is available to low-trust users and parserSafeMode is not enabled. Public CPE/product metadata in the bundle is incomplete, so asset identification may require local application inventory rather than scanner-only matching.

Exploitation context

No CISA KEV listing is provided and the bundle does not cite active exploitation. The issue requires an actor with page-edit capability and a later user interaction path. Vendor commentary says untrusted-user installations are expected to enable parserSafeMode=1 to prevent XSS.

Researcher notes

Evidence is limited to the CVE description and GitHub issue reference. The vendor disputes relevance under the documented safe-mode expectation, and the CVE bundle lists no concrete CPEs. Do not assume a patch, exploit activity, or broader affected versions beyond the sourced record.

Mitigation direction

  • Review Datenstrom Yellow guidance and the linked issue before changing production behavior.
  • Enable parserSafeMode=1 for installations accessible to untrusted users, per the vendor note.
  • Restrict page editing to trusted users until configuration is verified.
  • Check for a vendor-supported upgrade path or release guidance before relying on local fixes.

Validation and detection

  • Inventory any Datenstrom Yellow installations and confirm whether version 0.7.3 is present.
  • Inspect system/config/config.ini for parserSafeMode=1 on untrusted-accessible sites.
  • Review user roles to confirm only trusted users can edit pages.
  • Assess existing page content for unexpected embedded script or markup changes.
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-10726 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
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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

Source materials

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.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.