dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-11012

MEDIUM · 6.3 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 The Notibar – Notification Bar for WordPress plugin for WordPress is vulnerable to arbitrary shortcode execution via njt_nofi_text AJAX action in all versions up to, and including, 2.1.4. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes.

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 Notibar WordPress plugin has an authenticated arbitrary shortcode execution vulnerability in the njt_nofi_text AJAX action. The plugin passes user-supplied input directly to do_shortcode() without validation, allowing any authenticated user with Subscriber-level access or higher to execute arbitrary shortcodes.

MitigationUpdate to version 2.1.5 or later. If no update is available, disable the plugin. The fix requires adding proper input validation and capability checks before the do_shortcode call.

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
Low
Integrity
Low
Availability
Low

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

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 Notibar plugin is installed
    Check the WordPress plugins directory for the notibar folder, or list installed plugins via wp-admin > Plugins, or query the wp_options table for the active_plugins option
    Affected if Notibar plugin files exist in /wp-content/plugins/ or appears in the WordPress plugin list
  2. Determine installed Notibar version
    Check the plugin header in notibar.php for the Version field, or query the wp_options table where option_name contains 'notibar' version information
    Affected if Version is unknown, missing, or below 2.1.5 (the fixed version)
  3. Verify the vulnerable AJAX action exists
    Check plugin PHP files for the 'njt_nofi_text' action hook registered via add_action('wp_ajax_njt_nofi_text', ...) or wp_ajax_nopriv_njt_nofi_text
    Affected if The njt_nofi_text AJAX action is present and registered without capability checks
  4. Confirm do_shortcode usage with user input
    Review the AJAX handler function for do_shortcode() calls that process $_POST or $_REQUEST parameters directly without sanitization
    Affected if User-supplied POST/REQUEST data is passed directly to do_shortcode() without validation
  5. Identify user role configuration
    Check WordPress user roles in wp_users and wp_usermeta, or review if any Subscriber-level accounts exist on the site
    Affected if Any authenticated user with Subscriber role or higher can access the vulnerable AJAX endpoint

The environment is affected if the Notibar plugin is installed with a version below 2.1.5 and the njt_nofi_text AJAX action processes unsanitized user input through do_shortcode(), allowing any Subscriber-level user to execute arbitrary shortcodes.

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 version 2.1.5 or later. If no update is available, disable the plugin. The fix requires adding proper input validation and capability checks before the do_shortcode call.

Recommended fix Moderate confidence

The Notibar plugin version 2.1.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'The Notibar – Notification Bar' in the plugin list
  4. If an update is available, click 'Update Now' to update to version 2.1.5 or later
  5. Alternatively, navigate to Dashboard > Updates and select The Notibar plugin to update
  6. After updating, verify the plugin is running version 2.1.5 or higher
  7. Test that the notification bar functionality works as expected

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