LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1000840: Processing Foundation Processing version 3.4 and earlier contains a XML External Entity (XXE) vulnerability...

Processing Foundation Processing version 3.4 and earlier contains a XML External Entity (XXE) vulnerability in loadXML() function that can result in An attacker can read arbitrary files and exfiltrate their contents via HTTP requests. This attack appear to be exploitable via The victim must use Processing to parse a crafted XML document.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Processing 3.4 and earlier can mishandle XML parsing in loadXML(). If someone opens or processes a crafted XML document, the attacker may read local files and send their contents out over HTTP. Business risk depends on whether Processing is used with untrusted XML and whether sensitive files are accessible.

Executive priority

Treat this as a targeted data-exposure risk, not a broad internet-facing emergency. Prioritize teams that process external XML with Processing and systems holding sensitive local files.

Technical view

The CVE describes an XML External Entity vulnerability in Processing Foundation Processing loadXML() affecting version 3.4 and earlier. The stated impact is arbitrary file read with possible HTTP exfiltration. Exploitation requires the victim workflow to parse attacker-controlled XML. No CVSS score, CWE mapping, or vendor fix details are provided in the bundle.

Likely exposure

Exposure is likely limited to systems, tools, sketches, or applications using Processing 3.4 or earlier where loadXML() parses XML from users, partners, downloads, or other untrusted sources. Processing installations that do not parse external XML have lower practical exposure.

Exploitation context

The source bundle does not show active exploitation, and CISA KEV status is false. The described attack is not remote-by-default; it depends on a crafted XML document reaching a Processing loadXML() parsing workflow.

Researcher notes

Evidence is sparse: the CVE record names Processing 3.4 and earlier, loadXML(), XXE, arbitrary file read, and HTTP exfiltration. The bundle does not provide CVSS, detailed affected CPEs, patch version, CWE, proof of exploitation, or confirmed exploitation in the wild.

Mitigation direction

  • Avoid parsing untrusted XML with Processing loadXML() until vendor guidance is confirmed.
  • Check Processing project guidance and release notes for a fixed or safer version.
  • Restrict outbound HTTP from affected workstations or servers where practical.
  • Keep sensitive files away from environments that process untrusted XML.
  • Use XML parsing controls that disable external entities where configurable.

Validation and detection

  • Inventory Processing installations and identify versions 3.4 or earlier.
  • Review code and sketches for loadXML() use on external XML input.
  • Map XML sources: user uploads, partner feeds, downloads, or generated files.
  • Check whether affected environments can reach outbound HTTP destinations.
  • Confirm remediation against official Processing guidance before closing findings.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

cve · low confidence lookup

CVE-2018-1000840 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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