dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-11848

HIGH · 8.1 CVSS v3.1 Published 2025-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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 NitroPack plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'nitropack_dismiss_notice_forever' AJAX action in all versions up to, and including, 1.17.0. This makes it possible for authenticated attackers, with subscriber-level access and above, to update arbitrary options to a fixed value of '1' which can activate certain options (e.g., enable user registration) or modify certain options in a way that leads to a denial of service condition.

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 NitroPack WordPress plugin is vulnerable to broken access control. The 'nitropack_dismiss_notice_forever' AJAX action lacks a capability check, allowing any authenticated user with subscriber-level access or higher to update arbitrary WordPress options to a fixed value of '1'. This can enable dangerous settings like user registration or cause denial of service by modifying critical options.

MitigationUpdate to NitroPack version 1.17.1 or later which includes proper capability verification for the AJAX action. If immediate update is not possible, consider disabling the plugin or implementing a web application firewall rule to block the vulnerable endpoint.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 NitroPack plugin is installed
    Check your WordPress site's plugin directory or use 'wp plugin list' via WP-CLI to see if NitroPack is present and active
    Affected if NitroPack plugin is installed and active in WordPress
  2. Identify the installed NitroPack version
    Check the plugin header in wp-content/plugins/nitropack/includes/Plugin.php or use 'wp plugin get nitropack' via WP-CLI to retrieve the version number
    Affected if The installed version is lower than 1.17.1 (vulnerable versions)
  3. Confirm the vulnerable AJAX action exists
    Inspect the plugin PHP files for the 'nitropack_dismiss_notice_forever' action hook and verify it lacks a current_user_can() capability check before processing
    Affected if The AJAX action handler exists without a capability check or nonce verification
  4. Test AJAX endpoint accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=nitropack_dismiss_notice_forever using a low-privilege subscriber account to see if the request is processed
    Affected if The request is processed without a capability error (returns success rather than 403/401)
  5. Inspect critical WordPress options for unauthorized changes
    Query the wp_options table or use 'wp option list' to check if options like 'users_can_register', 'default_role', or other critical settings have been set to unexpected values, particularly '1'
    Affected if Critical options have been changed to values set by the vulnerable AJAX action (often '1')

You are affected if NitroPack is installed with a version below 1.17.1 and the vulnerable AJAX action can be invoked by any authenticated subscriber-level user.

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 to NitroPack version 1.17.1 or later which includes proper capability verification for the AJAX action. If immediate update is not possible, consider disabling the plugin or implementing a web application firewall rule to block the vulnerable endpoint.

Recommended fix Moderate confidence

Any version higher than 1.17.0

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the NitroPack plugin in the list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version of NitroPack from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is functioning correctly by accessing the NitroPack settings page.

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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-11848 — 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-11848 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