LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24567: WordPress Anything Order by Terms plugin <= 1.4.0 - Broken Access Control vulnerability

Missing Authorization vulnerability in briarinc Anything Order by Terms anything-order-by-terms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Anything Order by Terms: from n/a through <= 1.4.0.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24567 is a medium-severity access control flaw in the WordPress Anything Order by Terms plugin through version 1.4.0. A logged-in user may be able to perform actions they should not be authorized to perform, causing limited integrity impact. There is no source-provided evidence of active exploitation.

Executive priority

Treat as a routine but timely WordPress plugin remediation. Prioritize public-facing sites with user registration, contributor accounts, or many administrators. The business risk is unauthorized content or taxonomy changes, not broad compromise based on current public data.

Technical view

The issue is described as missing authorization, mapped to CWE-862. CVSS 3.1 is 4.3: network-accessible, low complexity, requires low privileges, no user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact. The public record identifies briarinc Anything Order by Terms plugin versions up to 1.4.0 as affected.

Likely exposure

Exposure is limited to WordPress sites with the Anything Order by Terms plugin installed at version 1.4.0 or earlier. The vulnerability requires an authenticated low-privilege user, so sites allowing user registration or many contributor-level accounts have higher practical risk.

Exploitation context

The available sources do not state that exploitation is occurring in the wild, and the CVE is not listed as KEV in the provided bundle. The flaw appears useful for unauthorized changes rather than data theft or service disruption, based on the CVSS impacts.

Researcher notes

Public details are sparse. The record identifies missing authorization but does not describe specific endpoints, permissions, exploit mechanics, or a confirmed fixed version. Avoid assuming unauthenticated exploitability; CVSS indicates privileges are required. Version data should be verified because the bundle contains both <=1.4.0 language and limited affected-version metadata.

Mitigation direction

  • Inventory WordPress sites for the Anything Order by Terms plugin.
  • If installed at version 1.4.0 or earlier, check vendor or Patchstack guidance.
  • Update if a fixed version is available from trusted sources.
  • Disable or remove the plugin if it is not business-critical.
  • Limit WordPress accounts to trusted users until remediation is confirmed.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress instance.
  • Record the installed plugin version and compare against <= 1.4.0.
  • Review user roles with access to plugin or taxonomy ordering features.
  • Check site change logs for unauthorized term ordering or configuration changes.
  • Monitor CVE, Patchstack, and plugin sources for updated remediation information.
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-24567 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
briarincAnything Order by Termsanything-order-by-terms, 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.