LiveActive security incident?Get immediate response
CVE Record

CVE-2020-35854: Textpattern 4.8.4 is affected by cross-site scripting (XSS) in the Body parameter.

Textpattern 4.8.4 is affected by cross-site scripting (XSS) in the Body parameter.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-35854 describes cross-site scripting in Textpattern 4.8.4 through the Body parameter. In business terms, unsafe content could execute in a user's browser if the vulnerable workflow is reachable. The provided sources do not include a CVSS score, patch version, or confirmed exploitation evidence.

Executive priority

Prioritize discovery first. If Textpattern 4.8.4 is Internet-facing or used by many authors, treat remediation as timely because XSS can support account compromise and content integrity risks. Without confirmed exposure, patch details, or exploitation evidence, this should not outrank actively exploited vulnerabilities.

Technical view

The CVE record states Textpattern 4.8.4 is affected by XSS in the Body parameter. The source bundle does not clarify whether this is stored or reflected XSS, required privileges, affected routes, fixed versions, or sanitization behavior. Treat the technical record as incomplete and validate against actual Textpattern exposure.

Likely exposure

Exposure is most likely limited to organizations running Textpattern 4.8.4, especially Internet-facing CMS instances or authoring interfaces. The CVE affected-product metadata is incomplete, so asset confirmation is required before scoping risk.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit reliability, or weaponized campaigns. It references a public write-up, but the provided evidence is insufficient to claim exploitation in the wild.

Researcher notes

Key gaps are CVSS, CWE, affected CPEs, privilege requirements, XSS type, vulnerable route, and fixed release. Do not extrapolate beyond Textpattern 4.8.4 and the Body parameter without checking primary project advisories or code history.

Mitigation direction

  • Inventory Textpattern deployments and confirm whether version 4.8.4 is present.
  • Check Textpattern vendor or project guidance for a fixed version or official workaround.
  • Restrict access to Textpattern authoring and administrative interfaces until remediated.
  • Review web application filtering controls as temporary defense, not a replacement for patching.

Validation and detection

  • Confirm Textpattern version from application administration or deployment records.
  • Identify whether the Body parameter workflow is reachable by untrusted users.
  • Review application logs for suspicious script-like content submissions.
  • Verify vendor guidance before declaring remediation complete.
Prepared
Confidence
medium
Sources
4

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-2020-35854 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
3Timeline events
1ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
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.