LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24542: WordPress WP Term Order plugin <= 2.1.0 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in John James Jacoby WP Term Order wp-term-order allows Cross Site Request Forgery.This issue affects WP Term Order: from n/a through <= 2.1.0.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24542 is a CSRF issue in the WordPress WP Term Order plugin through version 2.1.0. An attacker could trick a logged-in site user into unintentionally changing term ordering. Business impact appears limited to content or taxonomy integrity, not data theft or service outage, based on the published CVSS details.

Executive priority

Treat this as a moderate-priority WordPress hygiene issue. It is not described as actively exploited and does not indicate data theft, but it can affect site content integrity if administrators are tricked. Prioritize remediation for public-facing or business-critical WordPress sites using the plugin.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in John James Jacoby WP Term Order, package wp-term-order, affecting versions through 2.1.0. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality or availability impact, low integrity impact.

Likely exposure

Exposure is limited to WordPress sites using WP Term Order version 2.1.0 or earlier. The scenario likely depends on a logged-in user with relevant site privileges being induced to perform an unwanted action. Sites not using this plugin are not indicated as affected by the provided sources.

Exploitation context

The CVE record does not indicate active exploitation, and the source bundle marks CISA KEV as false. The attack class is CSRF, so exploitation generally relies on user interaction rather than direct unauthenticated compromise. Public evidence provided does not include exploit maturity or observed attacks.

Researcher notes

The source data is sparse and identifies the vulnerability class, affected range, CVSS vector, and Patchstack entry. It does not provide a named fixed version, proof of exploitation, or detailed vulnerable endpoint information. Avoid assuming exploitability beyond CSRF requiring user interaction and low integrity impact.

Mitigation direction

  • Inventory WordPress sites for the WP Term Order plugin.
  • Identify installations running WP Term Order 2.1.0 or earlier.
  • Check the plugin vendor or Patchstack page for fixed-version guidance.
  • Apply an available vendor-approved update if one is published.
  • Limit administrative access to trusted users until remediation is confirmed.
  • Educate administrators to avoid unexpected links while logged into WordPress.

Validation and detection

  • Confirm whether WP Term Order is installed on each WordPress site.
  • Record the installed plugin version for each instance.
  • Compare versions against the affected range: through 2.1.0.
  • Review vendor or Patchstack guidance for remediation status.
  • After remediation, verify the plugin version changed as expected.
  • Review recent administrative taxonomy changes for unexpected modifications.
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-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-24542 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:N/UI:R/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:N/UI:R/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-24542Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
John James JacobyWP Term Orderwp-term-order, 0unaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.