Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-15268: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in infility Infility Global

0
High
VulnerabilityCVE-2025-15268cvecve-2025-15268cwe-89
Published: Wed Feb 04 2026 (02/04/2026, 08:25:30 UTC)
Source: CVE Database V5
Vendor/Project: infility
Product: Infility Global

Description

The Infility Global plugin for WordPress is vulnerable to unauthenticated SQL Injection via the 'infility_get_data' API action in all versions up to, and including, 2.14.46. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append - with certain server configurations - additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 11:54:56 UTC

Technical Analysis

CVE-2025-15268 is an SQL Injection vulnerability identified in the Infility Global plugin for WordPress, affecting all versions up to and including 2.14.46. The vulnerability arises from insufficient escaping and lack of prepared statements in the 'infility_get_data' API action, which processes user-supplied parameters. Because the input is not properly sanitized, an unauthenticated attacker can craft malicious SQL payloads that append additional queries to the existing SQL commands executed by the plugin. This can lead to unauthorized disclosure of sensitive information stored in the backend database. The vulnerability does not require any authentication or user interaction, making it highly accessible to remote attackers. The CVSS v3.1 base score of 7.5 reflects a network attack vector with low complexity and no privileges required, impacting confidentiality but not integrity or availability. Although no public exploits are currently known, the vulnerability poses a significant risk due to the widespread use of WordPress and potential sensitive data exposure. The plugin’s failure to implement parameterized queries or adequate input validation is the root cause, highlighting a common security oversight in plugin development. Organizations using Infility Global should urgently review their installations and apply patches or mitigations once available.

Potential Impact

The primary impact of this vulnerability is the unauthorized disclosure of sensitive data from the database underlying WordPress sites using the Infility Global plugin. Attackers can exploit this flaw remotely without authentication, potentially extracting user credentials, personal information, or other confidential data. This can lead to privacy violations, regulatory non-compliance, reputational damage, and further exploitation such as account takeover or lateral movement within the network. Since the vulnerability does not affect data integrity or availability, it is less likely to cause service disruption but remains critical due to data confidentiality risks. Organizations with high-value or sensitive data hosted on affected WordPress sites are at particular risk. The ease of exploitation and lack of required privileges increase the likelihood of opportunistic attacks. Additionally, the absence of known exploits currently in the wild suggests a window of opportunity for defenders to mitigate before widespread exploitation occurs.

Mitigation Recommendations

1. Immediately disable or restrict access to the 'infility_get_data' API action if possible until a patch is available. 2. Apply any official patches or updates released by Infility addressing this vulnerability as soon as they are published. 3. Implement Web Application Firewall (WAF) rules to detect and block SQL injection payloads targeting the vulnerable API endpoint. 4. Conduct thorough input validation and sanitization on all user-supplied parameters, employing parameterized queries or prepared statements to prevent injection. 5. Monitor database logs and web server logs for unusual or suspicious query patterns indicative of SQL injection attempts. 6. Limit database user permissions to the minimum necessary to reduce the impact of potential exploitation. 7. Educate development teams on secure coding practices to avoid similar vulnerabilities in future plugin updates. 8. Consider isolating or sandboxing the WordPress environment to contain potential breaches. 9. Regularly audit installed plugins and remove any that are unused or unsupported to reduce attack surface.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-29T17:44:34.360Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69830729f9fa50a62f79eb60

Added to database: 2/4/2026, 8:45:29 AM

Last enriched: 2/27/2026, 11:54:56 AM

Last updated: 3/24/2026, 7:03:21 AM

Views: 61

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses