LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10102: Before WordPress 4.9.5, the version string was not escaped in the get_the_generator function, and could lea...

Before WordPress 4.9.5, the version string was not escaped in the get_the_generator function, and could lead to XSS in a generator tag.

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

Security readout for executives and security teams

Plain-English summary

CVE-2018-10102 is a WordPress core cross-site scripting issue fixed in WordPress 4.9.5. The problem was that a version string was not escaped before being placed in a generator tag. Older, unpatched WordPress sites may expose users or administrators to browser-side script execution.

Executive priority

Handle during normal vulnerability remediation, faster for public legacy WordPress. There is no cited active exploitation, but XSS in a major CMS can create account and trust risk if old sites remain exposed.

Technical view

Before WordPress 4.9.5, get_the_generator did not escape the version string before outputting it in a generator tag. The provided sources identify this as an XSS issue and point to WordPress core changeset 42893 and the matching GitHub commit as the fix evidence.

Likely exposure

Exposure is likely limited to WordPress core deployments older than 4.9.5, including packaged WordPress builds before their vendor security update. The bundle does not identify affected plugins, themes, or non-WordPress products.

Exploitation context

The bundle does not show CISA KEV listing, active exploitation, public exploit status, or attacker prerequisites. Treat internet-facing legacy WordPress as the main concern, but do not assume active abuse from these sources alone.

Researcher notes

Evidence is strong for the root cause and fix location, but incomplete for CVSS, exploitability conditions, and real-world exploitation. Avoid expanding affected scope beyond WordPress before 4.9.5 or relevant vendor packages named in the sources.

Mitigation direction

  • Upgrade WordPress core to 4.9.5 or later.
  • Apply Debian WordPress security updates where Debian packages are used.
  • Check current vendor guidance for supported upgrade paths.
  • Prioritize externally reachable and administrator-used WordPress sites.

Validation and detection

  • Inventory WordPress core versions across production and staging.
  • Flag any WordPress instance below 4.9.5.
  • For Debian systems, verify DSA-4193 or DLA-1366-1 coverage.
  • Confirm deployed source includes the referenced escaping fix.
Prepared
Confidence
medium
Sources
6

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-10102 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
8Source 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.