CVE-2026-1228
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2026-02-06

Last updated on: 2026-02-06

Assigner: Wordfence

Description
The Timeline Block – Beautiful Timeline Builder for WordPress (Vertical & Horizontal Timelines) plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.3.3 via the tlgb_shortcode() function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to disclose private timeline content via the id attribute supplied to the 'timeline_block' shortcode.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-06
Last Modified
2026-02-06
Generated
2026-05-07
AI Q&A
2026-02-06
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The Timeline Block – Beautiful Timeline Builder for WordPress plugin is vulnerable to an Insecure Direct Object Reference (IDOR) issue in all versions up to and including 1.3.3. This vulnerability exists in the tlgb_shortcode() function because it lacks proper validation on a user-controlled key.

As a result, authenticated attackers with Author-level access or higher can exploit this flaw to disclose private timeline content by manipulating the id attribute supplied to the 'timeline_block' shortcode.


How can this vulnerability impact me? :

This vulnerability allows attackers with Author-level access or above to access and disclose private timeline content that should otherwise be restricted.

Such unauthorized disclosure of private content can lead to information leakage, potentially exposing sensitive or confidential data to unauthorized users.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves the Timeline Block WordPress plugin versions up to 1.3.3, where an authenticated user with Author-level access can exploit the tlgb_shortcode() function by supplying a manipulated id attribute to the timeline_block shortcode to disclose private timeline content.

To detect if your system is vulnerable, first verify the installed version of the Timeline Block plugin. If it is version 1.3.3 or earlier, the system is vulnerable.

You can check the plugin version on your WordPress site by running the following command in the WordPress root directory:

  • wp plugin list --status=active | grep timeline-block

Alternatively, you can inspect the plugin version by checking the plugin's main file header or via the WordPress admin dashboard.

To detect exploitation attempts on your network, monitor HTTP requests for usage of the timeline_block shortcode with unusual or manipulated id parameters, especially from authenticated users with Author-level or higher privileges.

Since the vulnerability requires authenticated access, reviewing WordPress logs or web server logs for suspicious POST or GET requests containing the timeline_block shortcode with id parameters may help identify exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

The primary mitigation step is to update the Timeline Block plugin to version 1.3.4 or later, which contains the fix for CVE-2026-1228.

The update includes a comprehensive code refactor and security fix as detailed in changeset 3446078, addressing the insecure direct object reference vulnerability.

  • Backup your WordPress site and database before applying the update.
  • Update the plugin via the WordPress admin dashboard or by running the command:
  • wp plugin update timeline-block-block

If immediate updating is not possible, restrict Author-level user permissions or monitor and audit user activities closely to prevent exploitation.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart