CVE-2026-1127
Reflected XSS in WordPress Timeline Event History Plugin
Publication date: 2026-01-24
Last updated on: 2026-01-24
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | timeline_event_history | to 3.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the Timeline Event History WordPress plugin is a Reflected Cross-Site Scripting (XSS) issue via the 'id' parameter. This occurs because the plugin does not properly sanitize or escape input and output for this parameter in all versions up to and including 3.2. An unauthenticated attacker can exploit this by injecting malicious scripts into pages, which execute if a user is tricked into clicking a crafted link.
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary web scripts in the context of the affected site. This can lead to theft of user credentials, session hijacking, defacement, or redirection to malicious sites. Since it requires user interaction (clicking a link), it can be used in phishing attacks to compromise users visiting the vulnerable site.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing for reflected Cross-Site Scripting (XSS) via the `id` parameter in the Timeline Event History plugin pages. You can attempt to inject a simple script payload into the `id` parameter in URLs served by the plugin and observe if the script is reflected and executed. For example, you can use curl or a browser to send a request like: `http://yourwordpresssite.com/?id=<script>alert(1)</script>`. If the alert executes or the script is reflected in the response without proper sanitization, the vulnerability is present. Additionally, security scanners that test for reflected XSS vulnerabilities on WordPress plugins can be used.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Timeline Event History plugin to a version later than 3.2 where the vulnerability is fixed. If an update is not available, you should disable or remove the plugin to prevent exploitation. Additionally, applying Web Application Firewall (WAF) rules to block malicious payloads targeting the `id` parameter can help reduce risk. Educate users to avoid clicking suspicious links that may exploit this reflected XSS vulnerability.