LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24991: WordPress Extensions For CF7 plugin <= 3.4.0 - Insecure Direct Object References (IDOR) vulnerability

Authorization Bypass Through User-Controlled Key vulnerability in HT Plugins Extensions For CF7 extensions-for-cf7 allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Extensions For CF7: from n/a through <= 3.4.0.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24991 affects the WordPress plugin Extensions For CF7 by HT Plugins. Public data describes an IDOR authorization bypass that may let unauthenticated attackers access data they should not see. The recorded impact is limited to confidentiality, with no stated integrity or availability impact.

Executive priority

Treat as a moderate priority for WordPress owners. The issue is remotely reachable and unauthenticated, but the documented impact is limited confidentiality exposure and there is no source-confirmed active exploitation in the provided evidence.

Technical view

The issue is CWE-639, Authorization Bypass Through User-Controlled Key, in Extensions For CF7 through version 3.4.0. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges, no user interaction, with low confidentiality impact only. Public sources do not provide endpoint-level details or a named fixed version.

Likely exposure

Internet-facing WordPress sites using HT Plugins Extensions For CF7 version 3.4.0 or earlier are the likely exposure group. Sites not using this plugin are not indicated as affected.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The CVSS vector indicates exploitation is remotely reachable without authentication, but public evidence here does not include exploit availability or technical attack details.

Researcher notes

Public data is sparse. The CVE and Patchstack entry identify an IDOR/access-control flaw, but do not provide technical root cause, affected endpoints, exploit status, or fixed-version details in the supplied bundle. Avoid assuming broader impact than low confidentiality exposure.

Mitigation direction

  • Inventory WordPress sites for the Extensions For CF7 plugin.
  • Identify installations running version 3.4.0 or earlier.
  • Check HT Plugins, WordPress plugin, or Patchstack guidance for a fixed version.
  • Update the plugin if an official fixed release is available.
  • Disable or remove the plugin where it is not required.

Validation and detection

  • Confirm the plugin slug is extensions-for-cf7.
  • Record installed plugin versions across WordPress environments.
  • Flag versions 3.4.0 or earlier for remediation review.
  • Review access logs for unusual unauthenticated requests to plugin-related functionality.
  • Recheck CVE and Patchstack entries for updated fix 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 · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24991 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-24991Attack 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
HT PluginsExtensions For CF7extensions-for-cf7, 0unaffected
Weakness

CWE details

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

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.