LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32329: WordPress Advanced Related Posts plugin <= 1.9.1 - Broken Access Control vulnerability

Missing Authorization vulnerability in Ays Pro Advanced Related Posts advanced-related-posts allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Advanced Related Posts: from n/a through <= 1.9.1.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32329 affects the WordPress Advanced Related Posts plugin through version 1.9.1. It is a broken access control issue, meaning the plugin may allow actions without proper authorization. The published impact is limited integrity impact, not data theft or service outage. It matters mainly for WordPress sites using this specific plugin.

Executive priority

Treat as a moderate website integrity risk. It does not currently warrant emergency response absent exploitation evidence, but affected public WordPress sites should be identified and updated or de-risked promptly.

Technical view

The CVE describes CWE-862 Missing Authorization in Ays Pro Advanced Related Posts advanced-related-posts through <=1.9.1. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges or user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress installations with Advanced Related Posts installed at version 1.9.1 or earlier. The CVSS vector indicates remote unauthenticated reachability, but the public bundle does not identify specific vulnerable endpoints or actions.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Patchstack lists the issue as a vulnerability database entry. Public details are limited, so assume internet-facing WordPress sites with the plugin are the priority to review.

Researcher notes

Public information names missing authorization but does not provide endpoint-level detail, exploitability proof, or a specific fix in the supplied bundle. Avoid assuming broader WordPress impact. Focus analysis on plugin version presence, vendor release notes, and Patchstack updates.

Mitigation direction

  • Inventory WordPress sites for Advanced Related Posts and record installed versions.
  • If version is <=1.9.1, check vendor or Patchstack guidance for a fixed release.
  • Update the plugin if a fixed version is available from the vendor.
  • Disable or remove the plugin where it is not business-critical.
  • Monitor WordPress and web logs for unusual unauthenticated plugin-related activity.

Validation and detection

  • Confirm whether Advanced Related Posts is installed on each WordPress site.
  • Verify the plugin version is newer than 1.9.1, if an update exists.
  • Document sites where no fixed version or vendor guidance is available.
  • Review plugin changelogs and vendor advisories for authorization fixes.
  • Prioritize validation on public-facing WordPress sites.
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-32329 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:N/I:L/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:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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
Ays ProAdvanced Related Postsadvanced-related-posts, 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.