LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1127: Timeline Event History <= 3.2 - Reflected Cross-Site Scripting

The Timeline Event History plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the `id` parameter in all versions up to, and including, 3.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1127 affects the WordPress Timeline Event History plugin through version 3.2. A malicious link could cause script to run in a victim’s browser if they click it. This can support session theft or content manipulation risks, but it requires user interaction and is rated medium severity.

Executive priority

Treat as a moderate web risk. Prioritize internet-facing WordPress sites, especially those used by administrators or customers. The main urgency is reducing phishing-assisted browser compromise while waiting for or applying vendor guidance.

Technical view

The issue is reflected cross-site scripting in the plugin’s id parameter, caused by insufficient input sanitization and output escaping. It is unauthenticated, network-reachable, and requires user interaction. CVSS 3.1 is 6.1 with scope changed and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to WordPress sites using Timeline Event History versions up to and including 3.2. Sites not using this plugin are not affected based on the provided sources.

Exploitation context

No CISA KEV listing or cited source indicates active exploitation. Exploitation requires tricking a user into opening a crafted link, so phishing or targeted social engineering is the likely path.

Researcher notes

The source bundle states all versions up to 3.2 are vulnerable, while the structured affected entry is ambiguous. No patch version is provided. Analysis should rely on plugin inventory, version confirmation, and vendor guidance rather than assuming a fixed release.

Mitigation direction

  • Inventory WordPress sites for the Timeline Event History plugin.
  • Identify whether plugin version is 3.2 or earlier.
  • Check the vendor or WordPress plugin page for an updated release or guidance.
  • Disable or remove the plugin where business impact allows until guidance is available.
  • Monitor web and security logs for suspicious requests involving the affected parameter.

Validation and detection

  • Confirm plugin presence and version in WordPress administration or asset inventory.
  • Review whether the plugin is enabled on public-facing WordPress sites.
  • Verify any vendor-provided update has been applied when available.
  • Review security tooling for reflected XSS findings tied to this plugin.
Prepared
Confidence
high
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.

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-2026-1127 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
3Source 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-2026-1127Attack 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
wpdiscoverTimeline Event History0unaffected
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.