LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24962: WordPress Sigmize plugin <= 0.0.9 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Brainstorm Force Sigmize sigmize allows Cross Site Request Forgery.This issue affects Sigmize: from n/a through <= 0.0.9.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24962 is a cross-site request forgery issue in the WordPress Sigmize plugin through version 0.0.9. An attacker would need to trick an authorized user into taking an unintended action. The reported impact is limited integrity impact, not data theft or service outage. No active exploitation is indicated in the provided sources.

Executive priority

Treat as a routine but timely WordPress plugin hygiene issue. The business risk is moderate because exploitation requires user interaction and has limited integrity impact, but compromised admin actions can still affect site trust. Prioritize verification and vendor-guided remediation for sites using Sigmize.

Technical view

The vulnerability is CWE-352 CSRF affecting Brainstorm Force Sigmize WordPress plugin versions up to and including 0.0.9. CVSS 3.1 is 4.3 with network attack vector, low complexity, no privileges required by the attacker, and user interaction required. Scope is unchanged with low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites with the Sigmize plugin installed at version 0.0.9 or earlier. Sites without this plugin are not affected based on the provided sources. Internet-facing WordPress admin users increase practical risk because CSRF depends on a logged-in user being tricked.

Exploitation context

The attacker must induce a legitimate user, likely an authenticated WordPress administrator or privileged user, to interact with attacker-controlled content. The sources do not state public exploit availability or observed exploitation. CISA KEV status in the provided bundle is false.

Researcher notes

Available evidence is sparse. The CVE and Patchstack entry identify CSRF in Sigmize through 0.0.9, CVSS 4.3, and CWE-352. The provided sources do not describe affected endpoints, nonce validation details, a fixed version, exploit availability, or real-world exploitation.

Mitigation direction

  • Inventory WordPress sites for the Sigmize plugin and record installed versions.
  • Prioritize sites running Sigmize 0.0.9 or earlier for review.
  • Check Brainstorm Force, WordPress plugin, or Patchstack guidance for a fixed version.
  • Disable or remove the plugin where it is not business-critical.
  • Limit administrative browsing from active WordPress sessions where practical.

Validation and detection

  • Confirm whether Sigmize is installed on each WordPress site.
  • Verify the installed plugin version is above 0.0.9 if vendor guidance identifies a fixed release.
  • Review WordPress administrative roles for unnecessary privileged accounts.
  • Check change logs or security advisories before marking the issue remediated.
  • Document compensating controls if the plugin cannot be removed or updated.
Prepared
Confidence
high
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-24962 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-24962Attack 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
Brainstorm ForceSigmizesigmize, 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.