dbcve.org
Infility GlobalWordPress extension · Infility

CVE-2024-11496

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-07
Fix available
A fix is available. Upgrade to 2.9.9 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 Infility Global plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the infility_global_ajax function in all versions up to, and including, 2.9.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update plugin options and potentially break the site.

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 Infility Global WordPress plugin has a broken access control vulnerability in the infility_global_ajax function, which lacks a proper capability check. This allows any authenticated user with Subscriber-level access or higher to call this AJAX function and modify plugin settings, potentially causing site disruption.

MitigationUpdate the plugin to version 2.9.9 or later which should contain a proper capability check. If immediate update is not possible, consider restricting AJAX endpoint access or disabling the plugin until patched.

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
Infility GlobalWordPress extension
Affected:< 2.9.9

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. Check if Infility Global plugin is installed
    Look in the WordPress plugins directory (wp-content/plugins/) for a folder named 'infility-global' or 'infility-global-plugin', or check Plugins > Installed Plugins in wp-admin for the Infility Global plugin listing.
    Affected if The plugin appears in the WordPress plugins list
  2. Determine installed plugin version
    View the plugin details in wp-admin > Plugins > Installed Plugins, clicking on the Infility Global plugin to see its version number, or open the main plugin PHP file and look for the Version header in the plugin comment block.
    Affected if The installed version is below 2.9.9
  3. Check if AJAX functionality is enabled
    Look for the presence of AJAX action hooks in the plugin files, specifically searching for 'wp_ajax_infility_global_ajax' or 'wp_ajax_nopriv_infility_global_ajax' in the plugin PHP files.
    Affected if The AJAX endpoint 'infility_global_ajax' is registered and accessible
  4. Verify subscriber-level user accounts exist
    In wp-admin, go to Users > All Users and check if any users exist with the Subscriber role, or query the wp_usermeta table for users with wp_capabilities containing 'subscriber'.
    Affected if At least one user with Subscriber role or higher exists in WordPress

A WordPress site is affected if the Infility Global plugin version is below 2.9.9, the plugin's AJAX function is active, and any subscriber-level or higher user account exists 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
Upgrade available Upgrade to 2.9.9 or later
Fixed in 2.9.9
Interim mitigation

Update the plugin to version 2.9.9 or later which should contain a proper capability check. If immediate update is not possible, consider restricting AJAX endpoint access or disabling the plugin until patched.

Recommended fix High confidence

2.9.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Infility Global plugin
  4. If an update is available, click 'Update Now' to update to version 2.9.9 or higher
  5. Alternatively, navigate to Dashboard > Updates and select Infility Global to update
  6. After updating, verify the plugin version is 2.9.9 or later in the plugins list

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

Fix this in Infility Global Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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