Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) indicates a network-accessible vulnerability with low attack complexity and no privilege requirements, suggesting broad exploitability. However, the integrity impact is limited (I:L) with no confidentiality or availability impact, constraining the damage scope. Without confirmed KEV (CISA Known Exploited Vulnerabilities) status or public proof-of-concept code, the actual exploitation rate in the wild remains unknown. The EPSS score would be critical to cross-reference here, as a high EPSS coupled with no KEV status might indicate automated scanning activity without active weaponization. The low-to-moderate CVSS score (5.3) combined with network accessibility and no authentication barrier creates a real but bounded risk profile. Organizations should prioritize patching based on exposure (internet-facing deployment) and data sensitivity rather than CVSS score alone. If EPSS percentile is above 90%, exploit probability is high enough to warrant immediate patching; if below 50%, a standard patch cycle may be acceptable. |
| Exploit ScenarioDerived | An unauthenticated attacker discovers a Post Timeline instance exposed on the internet and sends a direct HTTP POST or PUT request to a timeline update endpoint, bypassing the authorization check due to misconfigured security levels. Because the attack vector is network-based and complexity is low, the attacker requires only a valid endpoint URL and basic knowledge of the API schema—often discoverable via browser developer tools or API documentation. The attacker successfully modifies timeline entries, project metadata, or user assignments, achieving data integrity impact without needing valid credentials or triggering any authentication challenges. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 13, 2026
Post Timeline versions 2.4.1 and earlier contain a missing authorization flaw that allows unauthenticated remote attackers to modify data by exploiting improperly configured access controls. The vulnerability enables integrity compromise without requiring user interaction or special privileges. No patch is currently available for this issue.
Earlier versions of this analysis (1)
A missing authorization vulnerability exists in Agile Logix Post Timeline versions through 2.4.1, where incorrectly configured access control security levels allow unauthenticated network attackers to modify data without authentication or user interaction. The vulnerability (CWE-862: Missing Authorization) has a CVSS score of 5.3 with network-based attack vector and low complexity, indicating moderate real-world risk with integrity impact but no confidentiality or availability impact.
RemediationAI
Immediately upgrade Agile Logix Post Timeline to version 2.4.2 or later, which should include authorization control fixes. Until patching is feasible, implement compensating controls: restrict network access to Post Timeline instances using firewall rules or security groups to allow only trusted internal IP ranges, enforce authentication at a reverse proxy layer with mutual TLS or API gateway authentication before requests reach the application, disable or revoke any API tokens or service accounts that interact with Post Timeline, and audit access logs for unauthorized modification attempts. If the application supports role-based access control configuration, review and enforce the principle of least privilege on all user accounts. Contact Agile Logix support for patch availability and timeline if a vendor advisory has not been published.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the Agile Logix Post Timeline application, a web-based timeline management tool. The root cause is classified under CWE-862 (Missing Authorization), which describes a failure to properly enforce access control policies at the application logic layer. Rather than a cryptographic or protocol-level flaw, this is a business logic vulnerability where the application fails to verify that the authenticated user (or unauthenticated requester) has permission to perform specific actions on protected resources. The affected product is identified via CPE as the Agile Logix Post Timeline component, with vulnerability present in versions up to and including 2.4.1. The issue manifests in how the application handles access control security level configurations, likely failing to validate authorization tokens, role-based access control (RBAC) rules, or attribute-based access control (ABAC) policies before processing state-modifying requests.
Know when Post Timeline gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
Missing Authorization vulnerability in Agile Logix Post Timeline post-timeline allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Post Timeline: from n/a through <= 2.4.1.
Executive ViewAI
Organizations using Missing Authorization vulnerability in Agile Logix Post Timeline post-timeline should be aware of moderate risk from CVE-2026-32421, a missing authorization vulnerability rated CVSS 5.3. Attackers could gain access beyond their authorized level. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Post Timeline
View allThe Post Timeline WordPress plugin before 2.3.10 does not sanitise and escape a parameter before outputting it back in t
The Post Timeline WordPress plugin before 2.2.6 does not sanitise and escape an invalid nonce before outputting it back
EUVD-2026-11947
NVD
CVE.org
EPSS
VulDB
GitHub PoC
Exploit-DB