What is the CVSS score of CVE-2026-4087?

CVE-2026-4087 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%.

Which versions of Pre Party Resource Hints are affected by CVE-2026-4087?

Organizations using all should be aware of notable risk from CVE-2026-4087, a SQL injection vulnerability rated CVSS 6.5. Exploitation could allow attackers to execute code or inject malicious input.

How to fix or mitigate CVE-2026-4087?

Within 30 days: Identify affected systems running all and apply vendor patches as part of regular patch cycle. Validate input sanitization for user-controlled parameters.

Pre Party Resource Hints CVE-2026-4087

EUVD-2026-14180 MEDIUM

SQL Injection (CWE-89)

2026-03-21 Wordfence

GHSA-342x-whc6-mjv9

WordPress SQLi Pre Party Resource Hints Wordpress Plugin

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Mar 21, 2026 - 04:00 euvd

EUVD-2026-14180

Analysis Generated

Mar 21, 2026 - 04:00 vuln.today

CVE Published

Mar 21, 2026 - 03:26 nvd

MEDIUM 6.5

DescriptionCVE.org

The Pre* Party Resource Hints plugin for WordPress is vulnerable to SQL Injection via the 'hint_ids' parameter of the pprh_update_hints AJAX action in all versions up to, and including, 1.8.20. 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 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 the Pre* Party Resource Hints WordPress plugin up to version 1.8.20 allows authenticated users with Subscriber-level permissions or higher to execute arbitrary database queries through the unescaped 'hint_ids' parameter in the pprh_update_hints AJAX action. An attacker can exploit this to extract sensitive information from the WordPress database without user interaction. No patch is currently available for this vulnerability.

Technical ContextAI

The vulnerability is rooted in CWE-89 (SQL Injection), a fundamental input validation failure where user-supplied data is concatenated directly into SQL queries without proper escaping or prepared statement usage. The affected product is the Pre* Party Resource Hints plugin for WordPress (CPE: cpe:2.3:a:samperrow:pre*_party_resource_hints), specifically in the AJAX handler at pprh_update_hints. Code inspection via the plugin's WordPress.org repository shows the vulnerability spans multiple files: Utils.php (line 80), DAO.php (lines 78 and 91), and LoadAdmin.php (line 72). The plugin uses WordPress's $wpdb API but fails to apply proper escaping functions (like $wpdb->prepare() with placeholders) when constructing SQL queries, allowing authenticated users to inject SQL metacharacters through the hint_ids parameter and execute arbitrary SELECT queries against the WordPress database.

RemediationAI

Update the Pre* Party Resource Hints plugin to a patched version beyond 1.8.20 as soon as available from the WordPress.org plugin repository or GitHub. If an immediate patch is unavailable, disable or remove the plugin entirely until a fix is released. As a temporary compensating control, restrict WordPress user role capabilities by disabling Subscriber registration or limiting the number of authenticated users with access to the site; implement database query logging and rate-limiting on AJAX endpoints to detect suspicious pprh_update_hints requests; enforce use of WordPress security plugins (e.g., Wordfence, Sucuri) that can detect and block SQL injection patterns; and ensure all WordPress core, theme, and plugin dependencies are kept up to date. Review Wordfence's advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/8ceb4750-0780-4437-a3b0-c4c4606f2715?source=cve) for vendor-specific patch timeline and technical details.