What is the CVSS score of CVE-2025-49421?

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

Which versions of Wordpress Plugin are affected by CVE-2025-49421?

A SQL injection vulnerability in the WP Text Expander WordPress plugin (versions through 1.0.1) allows attackers to potentially access, modify, or delete sensitive database information without proper…

How to fix or mitigate CVE-2025-49421?

Within 24 hours: Audit all WordPress installations to identify if WP Text Expander is installed and document affected systems. Within 7 days: Either deactivate and remove the plugin immediately, or implement network-level compensating controls (WAF rules blocking SQL injection patterns, database access restrictions). Within 30 days: Conduct forensic analysis of database logs for signs of exploitation; implement security monitoring for SQL injection attempts; evaluate alternative text expansion plugins with established security records.

Wordpress Plugin CVE-2025-49421

EUVD-2025-17302 HIGH

SQL Injection (CWE-89)

2025-06-06 audit@patchstack.com

WordPress SQLi Wordpress Plugin

7.6

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.6 HIGH

AV:N/AC:L/PR:H/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

High

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 - 18:10 euvd

EUVD-2025-17302

Analysis Generated

Mar 14, 2026 - 18:10 vuln.today

CVE Published

Jun 06, 2025 - 13:15 nvd

HIGH 7.6

DescriptionCVE.org

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Andrei Filonov WP Text Expander allows SQL Injection. This issue affects WP Text Expander: from n/a through 1.0.1.

AnalysisAI

SQL injection vulnerability in Andrei Filonov's WP Text Expander WordPress plugin (versions through 1.0.1) that allows authenticated attackers with high-privilege administrative roles to execute arbitrary SQL queries. The vulnerability has a CVSS score of 7.6 (high severity) due to its ability to achieve confidentiality compromise and limited availability impact, though it requires administrative credentials to exploit. No current KEV (Known Exploited Vulnerability) status or public proof-of-concept is indicated in the provided data, suggesting limited real-world active exploitation at present.

Technical ContextAI

The vulnerability stems from improper neutralization of special SQL metacharacters (CWE-89: Improper Neutralization of Special Elements used in an SQL Command) within the WP Text Expander plugin. This is a classic SQL injection flaw where user-controlled or plugin-controlled input is concatenated directly into SQL queries without parameterized prepared statements or proper escaping. The affected product is a WordPress plugin (CPE likely wp:wp_text_expander or similar), which extends WordPress functionality and operates within the WordPress plugin architecture. WP Text Expander likely processes text expansion queries that interact with the WordPress database layer, and the injection point exists where these queries are constructed. The vulnerability class (CWE-89) indicates failure to use parameterized queries or sufficient input validation when building dynamic SQL statements.

RemediationAI

Immediate remediation options: (1) Update WP Text Expander to a version newer than 1.0.1 if a patch is released by Andrei Filonov—check wordpress.org/plugins/wp-text-expander for available updates; (2) If no patch is available, disable and deactivate the WP Text Expander plugin until a fix is released; (3) Implement strict access controls to limit WordPress administrator accounts to trusted users only, reducing the attack surface given the PR:H requirement; (4) If the plugin must remain active, apply Web Application Firewall (WAF) rules to detect and block SQL injection patterns in admin requests targeting the plugin; (5) Review access logs and WordPress user activity for any suspicious admin-level database queries. Patch information and advisory should be published on the plugin's wordpress.org page or the vendor's security advisory channel—monitor these for remediation releases.