CVE-2026-4087
SQL Injection in Pre* Party Resource Hints Plugin Allows Data Exposure
Publication date: 2026-03-21
Last updated on: 2026-03-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| pre_party_resource_hints | pre_party_resource_hints | to 1.8.20 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Pre* Party Resource Hints plugin for WordPress has a vulnerability in the 'hint_ids' parameter of the pprh_update_hints AJAX action. This vulnerability is a SQL Injection caused by insufficient escaping of user input and lack of proper preparation of the SQL query.
Authenticated attackers with Subscriber-level access or higher can exploit this vulnerability by appending additional SQL queries to existing ones, potentially extracting sensitive information from the database.
How can this vulnerability impact me? :
This vulnerability allows attackers with at least Subscriber-level access to perform SQL Injection attacks, which can lead to unauthorized extraction of sensitive information from the database.
Such unauthorized data access can compromise the confidentiality of your data and potentially expose sensitive user or system information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know