dbcve.org
Styler For Ninja FormsWordPress extension · Wpmonks

CVE-2024-10717

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to after 3.3.4 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Styler for Ninja Forms plugin for WordPress is vulnerable to unauthorized modification of data that can lead to a denial of service due to a missing capability check on the deactivate_license function in all versions up to, and including, 3.3.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary option values on the WordPress site. This can be leveraged to delete an option that would create an error on the site and deny service to legitimate users. Note: This issue can also be used to add arbitrary options with an empty value.

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 Styler for Ninja Forms plugin for WordPress lacks a capability check on the deactivate_license function, allowing any authenticated user with Subscriber-level access or higher to delete arbitrary WordPress options or add empty options. This broken access control can be exploited to cause denial of service by deleting critical site options.

MitigationUpdate to plugin version 3.3.5 or later which includes proper capability verification on the deactivate_license function. If immediate patching is not feasible, consider temporarily disabling user registration or the plugin until the update can be applied.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Styler For Ninja FormsWordPress extension
Affected:<= 3.3.4

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
High
Availability
None

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

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 Styler For Ninja Forms plugin is installed
    Go to WordPress admin > Plugins and look for 'Styler For Ninja Forms' or check via wp-cli: wp plugin list --name='styler-for-ninja-forms'
    Affected if Plugin is installed and version is 3.3.4 or lower
  2. Check installed plugin version
    View plugin details in WordPress admin plugins list, or check the plugin main file header version constant, or use: grep -r 'Version:' wp-content/plugins/styler-for-ninja-forms/
    Affected if Version displayed is 3.3.4 or any version below 3.3.5
  3. Confirm user registration is enabled
    Go to WordPress admin > Settings > General > Membership: ensure 'Anyone can register' is unchecked, or check via wp-cli: get_option('users_can_register')
    Affected if 'Anyone can register' is enabled AND new users can be assigned Subscriber role
  4. Check for existing Subscriber-level users
    Go to WordPress admin > Users and filter by Subscriber role, or use: wp user list --role=subscriber
    Affected if Any Subscriber-level user accounts exist (excluding your own admin account)
  5. Verify the missing capability check in plugin code
    Inspect the deactivate_license function in the plugin file (typically in includes/admin or classes folder) - look for current_user_can() check before the function executes, or check if nonce verification without capability check exists
    Affected if The deactivate_license function lacks a current_user_can() capability check (vulnerable) or has only nonce check without capability verification

User is affected if Styler For Ninja Forms version 3.3.4 or lower is installed AND either user registration is open to Subscribers OR any Subscriber accounts already exist in the system.

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.

From vendor data
Upgrade available Upgrade to a release after 3.3.4
Interim mitigation

Update to plugin version 3.3.5 or later which includes proper capability verification on the deactivate_license function. If immediate patching is not feasible, consider temporarily disabling user registration or the plugin until the update can be applied.

Fix this in Styler For Ninja Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10717 — 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-10717 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