dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-1945

HIGH · 7.1 CVSS v3.1 Published 2024-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Contact Form, Survey & Popup Form Plugin for WordPress – ARForms Form Builder plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'arflite_remove_preview_data' function in all versions up to, and including, 1.6.4. This makes it possible for authenticated attackers, with subscriber access and above, to delete arbitrary site options, resulting in loss of availability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ARForms Form Builder plugin for WordPress contains a broken access control vulnerability where the 'arflite_remove_preview_data' function lacks a capability check, allowing authenticated users with subscriber-level access to delete arbitrary WordPress site options. This results in loss of availability as critical site configuration data can be erased.

MitigationUpdate the ARForms Form Builder plugin to version 1.6.5 or later which implements proper capability validation on the affected function. Before updating, create a full site backup and test the update in a staging environment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify ARForms plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate ARForms Form Builder. Check the version number displayed under the plugin name. Alternatively, check the main plugin file (arforms.php) for the 'Version' header comment.
    Affected if The installed version is earlier than 1.6.5 (the version that contains the fix)
  2. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that ARForms Form Builder shows as 'Active' under the plugin status.
    Affected if The plugin is active and the version is below 1.6.5
  3. Identify subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the list for any accounts with the 'Subscriber' role. Count how many subscriber accounts exist on the site.
    Affected if There is at least one active subscriber-level user account and the plugin version is below 1.6.5
  4. Inspect the vulnerable function file
    Locate the ARForms plugin files via FTP or file manager. Navigate to the includes or core folder and search for the function named 'arflite_remove_preview_data'. Verify the function exists and lacks a capability check (look for missing 'current_user_can' or similar authorization call).
    Affected if The function exists in the plugin files and contains no capability validation before performing the option deletion operation

You are affected if the ARForms Form Builder plugin is active with a version earlier than 1.6.5 and subscriber-level user accounts exist on the site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the ARForms Form Builder plugin to version 1.6.5 or later which implements proper capability validation on the affected function. Before updating, create a full site backup and test the update in a staging environment.

Recommended fix Moderate confidence

1.6.5 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find ARForms Form Builder in the plugin list
  4. Check if the current version is 1.6.4 or earlier
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects the patched release
Caveat Minor plugin version updates typically do not introduce breaking changes; always backup site before updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1945 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1945 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data