dbcve.org
Infility GlobalWordPress extension · Infility

CVE-2024-12290

MEDIUM · 6.1 CVSS v3.1 Published 2025-01-07
Fix available
A fix is available. Upgrade to 2.9.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Reflected Cross-Site Scripting via the ‘set_type’ parameter in all versions up to, and including, 2.9.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE-2024-12723 is a duplicate of this issue.

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 (versions up to 2.9.8) is vulnerable to reflected Cross-Site Scripting (XSS) via the 'set_type' parameter. Due to insufficient input sanitization and inadequate output escaping, unauthenticated attackers can inject malicious JavaScript through crafted URLs. Successful exploitation requires tricking a user into clicking a malicious link.

MitigationUpdate the Infility Global plugin to version 2.9.9 or later, which contains the fix for this vulnerability. As an interim measure, caution users against clicking untrusted links.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm Infility Global plugin is installed
    Access your WordPress site via FTP or file manager and check the wp-content/plugins directory for a folder named 'infility-global' or similar infility-related folder
    Affected if The plugin folder exists in wp-content/plugins
  2. Identify the installed plugin version
    Open the main plugin PHP file (often named infility-global.php or similar) and locate the version definition in the plugin header comment, or check readme.txt for the Version field
    Affected if The reported version is below 2.9.9 (versions 2.9.8 and earlier are affected)
  3. Verify the vulnerable parameter is accessible
    Check if the WordPress frontend or any public-facing page loads the Infility Global plugin functionality that handles the 'set_type' parameter in HTTP requests
    Affected if The plugin exposes functionality that processes the set_type parameter without authentication
  4. Test for reflected XSS condition
    Review the plugin source code for the set_type parameter handling - look for $_GET['set_type'] or similar without sanitize_text_field, esc_html, or esc_url encoding before output
    Affected if The code outputs the set_type parameter value without proper sanitization and escaping

You are affected if the Infility Global plugin is installed with a version below 2.9.9 and the code handling the set_type parameter lacks proper input sanitization and output escaping.

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 Infility Global plugin to version 2.9.9 or later, which contains the fix for this vulnerability. As an interim measure, caution users against clicking untrusted links.

Recommended fix High confidence

Infility Global version 2.9.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Infility Global plugin in the list
  4. Click Update Now or navigate to the plugin's details and click Update to version 2.9.9
  5. Wait for the update to complete and verify the plugin shows version 2.9.9 or higher
  6. Clear any caching mechanisms if the site uses caching plugins or server-side caching

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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