LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24374: WordPress RegistrationMagic plugin <= 6.0.6.9 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Metagauss RegistrationMagic custom-registration-form-builder-with-submission-manager allows Cross Site Request Forgery.This issue affects RegistrationMagic: from n/a through <= 6.0.6.9.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the WordPress RegistrationMagic plugin through version 6.0.6.9. It is a CSRF issue, meaning an attacker may trick a logged-in user into causing unintended changes. The public record rates it medium severity. No source provided here confirms active exploitation.

Executive priority

Treat as a routine but timely WordPress plugin remediation item. Prioritize internet-facing business sites, sites with high-value registrations, and sites where administrators frequently manage forms. Current evidence supports medium urgency, not emergency response.

Technical view

CVE-2026-24374 is CWE-352 in Metagauss RegistrationMagic package custom-registration-form-builder-with-submission-manager through 6.0.6.9. CVSS 3.1 is 5.4: network exploitable, low complexity, no attacker privileges, user interaction required, with low integrity and availability impact and no confidentiality impact.

Likely exposure

Exposure is likely limited to WordPress sites running RegistrationMagic version 6.0.6.9 or earlier. Sites without the plugin, or with versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The issue requires user interaction and is consistent with tricking a victim’s browser into submitting an unwanted request. The CVE is not listed as CISA KEV in the provided data, and no cited source confirms exploitation in the wild.

Researcher notes

The source bundle names CSRF but does not describe the vulnerable endpoint, required victim role, patched version, or concrete remediation. Avoid assuming exploitability details beyond CVSS and CWE. Validate against the vendor advisory or plugin changelog before closing remediation.

Mitigation direction

  • Inventory WordPress sites for the RegistrationMagic plugin and installed version.
  • Check Metagauss, WordPress plugin repository, and Patchstack for vendor remediation guidance.
  • Update beyond 6.0.6.9 if a fixed version is identified by the vendor.
  • If no fix is available, evaluate temporarily disabling the plugin based on business need.
  • Limit administrative sessions and educate privileged users about suspicious links.

Validation and detection

  • Confirm whether custom-registration-form-builder-with-submission-manager is installed.
  • Record the plugin version and compare it to the affected range: through 6.0.6.9.
  • Review vendor or Patchstack advisories for fixed-version confirmation.
  • Check for unexpected RegistrationMagic configuration or form changes.
  • Track CVE and advisory updates for exploit or remediation changes.
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-24374 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.4 (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:L

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.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-24374Attack 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:L

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
MetagaussRegistrationMagiccustom-registration-form-builder-with-submission-manager, 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.