What is the CVSS score of EUVD-2025-17523?

EUVD-2025-17523 has a CVSS 3.1 base score of 8.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L. EPSS exploitation probability: 0.1%.

Which versions of Wordpress Plugin are affected by EUVD-2025-17523?

A SQL injection vulnerability in Infility Global versions 2.12.4 and earlier allows attackers to potentially access, modify, or delete sensitive database information without authorization.

How to fix or mitigate EUVD-2025-17523?

Within 24 hours: Inventory all Infility Global instances and document versions in use; restrict database access to trusted networks only. Within 7 days: Implement WAF rules to detect and block SQL injection patterns targeting Infility Global; disable non-critical features if possible to reduce attack surface. Within 30 days: Establish timeline for upgrade to patched version once available; consider alternative solutions if vendor patch timeline is unacceptable; conduct database audit for unauthorized access logs.

Wordpress Plugin EUVD-2025-17523

| CVE-2025-47651 HIGH

SQL Injection (CWE-89)

2025-06-09 audit@patchstack.com

WordPress SQLi Wordpress Plugin

8.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.5 HIGH

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

Low

Lifecycle Timeline

Re-analysis Queued

Apr 23, 2026 - 15:42 vuln.today

cvss_changed

EUVD ID Assigned

Mar 14, 2026 - 19:21 euvd

EUVD-2025-17523

Analysis Generated

Mar 14, 2026 - 19:21 vuln.today

CVE Published

Jun 09, 2025 - 16:15 nvd

HIGH 8.5

DescriptionCVE.org

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Infility Infility Global allows SQL Injection. This issue affects Infility Global: from n/a through 2.12.4.

AnalysisAI

A SQL injection vulnerability in Infility Global (CWE-89) allows authenticated attackers to execute arbitrary SQL queries with network access, potentially leading to unauthorized data disclosure and limited availability impact. The vulnerability affects Infility Global versions up to and including 2.12.4, and the CVSS 8.5 score reflects high confidentiality impact; however, without confirmation of active exploitation (KEV status) or public POC availability, real-world risk depends on deployment prevalence and attacker motivation.

Technical ContextAI

This vulnerability represents improper neutralization of special SQL metacharacters in user-supplied input passed to SQL command execution contexts (CWE-89: SQL Injection). The flaw exists in Infility Global, an enterprise application platform used for business process management and data integration. The affected component fails to implement parameterized queries or input validation/sanitization before constructing SQL statements. Attackers with valid credentials (PR:L in CVSS vector) can inject malicious SQL syntax to bypass query logic, extract sensitive data from backend databases, or manipulate query results. The scope change (S:C) indicates the vulnerability can affect resources beyond the vulnerable application component itself, suggesting shared database resources or cross-application data exposure.

RemediationAI

Immediate: Upgrade Infility Global to the first patched version after 2.12.4 (presumed 2.12.5 or later pending vendor confirmation). 2) Interim mitigations pending patch deployment: (a) Restrict network access to Infility Global to trusted IP ranges and VPNs to reduce attack surface despite PR:L requirement; (b) Implement database activity monitoring (DAM) to detect anomalous SQL queries executed by compromised or malicious accounts; (c) Apply least-privilege database account permissions, limiting application service accounts to minimum necessary SQL operations; (d) Conduct code review of custom SQL query construction in Infility Global modules to identify and remediate similar injection flaws. 3) Post-remediation: Update to 2.12.5+ and validate patch installation through vendor testing procedures. Reference: Contact Infility support or check official security advisories at [vendor advisory URL—to be obtained from vendor security page].