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

CVE-2025-10175 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

WordPress CVE-2025-10175

MEDIUM

SQL Injection (CWE-89)

2025-10-11 security@wordfence.com

WordPress SQLi

6.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Apr 08, 2026 - 19:39 vuln.today

CVE Published

Oct 11, 2025 - 10:15 nvd

MEDIUM 6.5

DescriptionCVE.org

The WP Links Page plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter in all versions up to, and including, 4.9.6 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

AnalysisAI

SQL injection in WP Links Page plugin for WordPress (all versions up to 4.9.6) allows authenticated attackers with Subscriber-level access and above to extract sensitive database information via the unescaped 'id' parameter. The vulnerability stems from insufficient input sanitization and lack of prepared statements, enabling attackers to append arbitrary SQL queries to existing database operations. CVSS 6.5 reflects the high confidentiality impact for authenticated remote exploitation with low attack complexity; no public exploit code or active exploitation has been confirmed at analysis time.

Technical ContextAI

The vulnerability is a classic SQL Injection (CWE-89) flaw in the WP Links Page WordPress plugin, affecting versions through 4.9.6. The root cause is the plugin's failure to properly escape or parameterize the 'id' parameter before incorporating it into SQL queries. WordPress plugins should leverage the wpdb API with prepared statements (using placeholders and wpdb::prepare()) or properly escape user input via esc_sql() and related sanitization functions. The 'id' parameter in this plugin appears to be used in a database lookup operation without these protections, allowing an attacker to inject additional SQL syntax (e.g., UNION, OR, subqueries) to read arbitrary table data. The presence of Subscriber-level access requirement indicates the plugin likely processes this parameter in an authenticated context (e.g., admin-facing link management functionality).

Affected ProductsAI

The WP Links Page plugin for WordPress is vulnerable in all versions up to and including 4.9.6. The plugin is hosted on the WordPress plugin repository at wordpress.org/plugins/wp-links-page/ and the source code repository at plugins.svn.wordpress.org/wp-links-page/. The vulnerability affects any WordPress installation running this plugin at version 4.9.6 or earlier. Organizations using this plugin should immediately identify and assess their installations.

RemediationAI

Users must update the WP Links Page plugin to a patched version released after 4.9.6. The fix, as referenced in the WordPress plugin trac repository changeset (sfp_email=&sfph_mail=&reponame=&old=3410752%40wp-links-page&new=3410752%40wp-links-page), involved correcting the SQL query preparation and input escaping for the 'id' parameter. WordPress administrators should navigate to their plugin management dashboard, verify the latest available version of WP Links Page, and upgrade immediately. If a patched version is not yet available, administrators should consider disabling the plugin until a fix is released. The Wordfence vulnerability advisory at wordfence.com/threat-intel/vulnerabilities/id/cb753b29-ca8c-4044-97ff-3b7e57d5de61 provides detailed technical information and may include additional mitigation guidance.