Plugins · timeline-event-history · data as of 2026-11-04
Is Timeline Event History safe? Known vulnerabilities and latest version
- Status
- Closed 2026-01-22
- Known issues on record
- 4
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate timeline-event-history && wp plugin delete timeline-event-history
Check your version
Known vulnerabilities
4 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 4 record(s) do not state which versions are affected.
high 7.1 CVE-2025-69384 · published 2026-02-20
Reflected cross-site scripting (XSS) in Timeline Event History (3.2 and older)
- Affected
- 3.2 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpdiscover Timeline Event History timeline-event-history allows Reflected XSS.This issue affects Timeline Event History: from n/a through <= 3.2.
medium 6.1 CVE-2026-1127 · published 2026-01-24
Reflected cross-site scripting (XSS) in Timeline Event History (3.2 and older)
- Affected
- 3.2 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
medium 6.5 CVE-2025-31595 · published 2025-03-31
Stored cross-site scripting (XSS) in Timeline Event History (3.2 and older)
- Affected
- 3.2 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpdiscover Timeline Event History timeline-event-history allows Stored XSS.This issue affects Timeline Event History: from n/a through <= 3.2.
high 8.8 CVE-2024-5726 · published 2024-07-18
PHP object injection in Timeline Event History (3.1 and older)
- Affected
- 3.1 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Timeline Event History plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.1 via deserialization of untrusted input 'timelines-data' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
NVD CVE-2024-5726Wordfence advisoryCode change (fix)Plugin source
Recent activity
- 2026-01-22 — closed on wordpress.org (Security Issue).
- 2026-02-20 — Reflected cross-site scripting (XSS) disclosed (CVE-2025-69384), fix version not stated.
- 2026-01-24 — Reflected cross-site scripting (XSS) disclosed (CVE-2026-1127), fix version not stated.
- 2025-03-31 — Stored cross-site scripting (XSS) disclosed (CVE-2025-31595), fix version not stated.
Get an email when Timeline Event History has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Timeline Event History (timeline-event-history) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (3) · PHP object injection (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/timeline-event-history (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/timeline-event-history"><img src="https://laskyr.com/plugins/timeline-event-history/badge.svg" alt="Timeline Event History vulnerability status"></a>