LiveActive security incident?Get immediate response
CVE Record

CVE-2024-1218: Contact Form builder with drag & drop for WordPress – Kali Forms <= 2.3.41 - Missing Authorization

The Contact Form builder with drag & drop for WordPress – Kali Forms plugin for WordPress is vulnerable to unauthorized access and modification of data via API due to an inconsistent capability check on several REST endpoints in all versions up to, and including, 2.3.41. This makes it possible for authenticated attackers, with contributor access and higher, to obtain access to or modify forms or entries.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects the Kali Forms WordPress plugin when installed at versions up to and including 2.3.41. A logged-in user with Contributor-level access or higher could reach REST API functions they should not have, potentially exposing or changing form and entry data.

Executive priority

Treat this as a moderate-priority WordPress hardening item. It is not documented as actively exploited, but affected sites with many content contributors should remediate promptly because form submissions can contain customer or lead data.

Technical view

CVE-2024-1218 is a CWE-862 missing authorization flaw caused by inconsistent capability checks on several Kali Forms REST endpoints. The CVSS 3.1 score is 4.3. The CVE description states authenticated Contributor+ users can obtain access to or modify forms or entries; the supplied CVSS vector records low confidentiality impact only.

Likely exposure

Exposure is limited to WordPress sites running Kali Forms <= 2.3.41 where users with Contributor or higher roles are present, especially multi-author, agency, membership, or client-managed sites.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Abuse requires authenticated WordPress access with at least Contributor privileges, so risk depends heavily on account hygiene and role assignment.

Researcher notes

The affected-version evidence comes from the CVE description and Wordfence title. The source bundle’s affected object lists version “0” with defaultStatus “unaffected,” which appears incomplete or inconsistent. Use plugin version checks and the upstream changeset for validation.

Mitigation direction

  • Inventory WordPress sites for Kali Forms and confirm installed versions.
  • Update Kali Forms to a vendor-supported release beyond 2.3.41 if available.
  • Review vendor and WordPress plugin guidance for the exact fixed release.
  • Restrict Contributor and higher roles to trusted users only.
  • Review recent form and entry changes for unexpected activity.

Validation and detection

  • Check each WordPress site for the Kali Forms plugin version.
  • Identify all accounts with Contributor, Author, Editor, or Administrator roles.
  • Confirm untrusted users cannot access Kali Forms administrative REST functionality.
  • Review web and WordPress audit logs for unusual form or entry access.
  • Verify the installed plugin includes the authorization changes referenced by the WordPress changeset.
Prepared
Confidence
medium
Sources
4

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-2024-1218 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: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
3Source 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:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
wpchillKali Forms — Contact Form & Drag-and-Drop Builder0unaffected
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.