LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32421: WordPress Post Timeline plugin <= 2.4.1 - Broken Access Control vulnerability

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32421 is a medium-severity access control issue in the WordPress Post Timeline plugin by Agile Logix, affecting versions through 2.4.1. An unauthenticated remote attacker may be able to access information they should not. The public data does not show active exploitation or a named fixed version.

Executive priority

Treat as a routine but timely remediation item for public WordPress sites. It is not currently supported as an emergency vulnerability by KEV or cited exploitation evidence, but unauthenticated access-control weaknesses on internet-facing CMS plugins should not remain unresolved.

Technical view

The issue is CWE-862 Missing Authorization in post-timeline. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact, no integrity or availability impact. The CVE description attributes the flaw to incorrectly configured access control security levels.

Likely exposure

Exposure is likely limited to WordPress sites with the Agile Logix Post Timeline plugin installed at version 2.4.1 or earlier. Internet-facing WordPress sites are the primary concern because the CVSS vector indicates network access and no authentication required.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not listed as KEV. The risk is unauthorized information access rather than site takeover based on the published CVSS impacts. Public technical detail is limited in the provided sources.

Researcher notes

Public evidence identifies missing authorization but does not provide endpoint-level detail in the supplied bundle. Avoid assuming write access, privilege escalation, or remote code execution. Validate scope against the plugin version and wait for vendor or Patchstack details before making stronger exploitation claims.

Mitigation direction

  • Inventory WordPress sites for the Post Timeline plugin and version.
  • Prioritize sites running Post Timeline version 2.4.1 or earlier.
  • Check Agile Logix, WordPress plugin, or Patchstack guidance for an updated version or workaround.
  • Disable the plugin if it is unnecessary and no vendor fix is available.
  • Apply compensating access controls where feasible until vendor guidance is confirmed.

Validation and detection

  • Confirm whether the post-timeline plugin is installed on each WordPress site.
  • Record installed plugin versions and compare against <= 2.4.1.
  • Review vendor or Patchstack advisory status for fixed-version information.
  • Check web logs for unusual unauthenticated access to plugin-related endpoints.
  • Document remediation status for each affected WordPress instance.
Prepared
Confidence
medium
Sources
3

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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-32421 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
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
2Source 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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-32421Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
Agile LogixPost Timelinepost-timeline, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.