dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4087

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Pre* Party Resource Hints WordPress plugin versions up to 1.8.20 contain a SQL injection vulnerability in the pprh_update_hints AJAX action. The 'hint_ids' parameter is not properly escaped before being used in a SQL query, and the query lacks prepared statements, allowing authenticated attackers with Subscriber-level access to inject arbitrary SQL and extract sensitive database information.

MitigationUpdate the plugin to the latest patched version (1.8.21 or higher). If no patch is available, disable the plugin immediately or restrict AJAX functionality via firewall rules until a fix is deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the plugin is installed
    Check if the Pre* Party Resource Hints plugin directory exists in wp-content/plugins/ or list installed plugins via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed version
    View the plugin's main PHP file header (usually in wp-content/plugins/pre-party-resource-hints/) or check the plugin's readme.txt for the Version field
    Affected if The version listed is 1.8.20 or lower, or no version is displayed (indicating an old unpatched install)
  3. Verify the vulnerable AJAX action exists
    Search the plugin files for 'pprh_update_hints' in the AJAX action hook registration (look for add_action('wp_ajax_pprh_update_hints' or similar)
    Affected if The code contains the pprh_update_hints AJAX action without sanitization on the hint_ids parameter
  4. Check if subscriber-level accounts exist
    Navigate to Users > All Users in WordPress admin or query the wp_users and wp_usermeta tables to list users with the Subscriber role
    Affected if There is at least one user account with Subscriber-level access or lower that can access the site
  5. Determine if AJAX endpoints are accessible to subscribers
    Test accessing /wp-admin/admin-ajax.php?action=pprh_update_hints with a subscriber-level account's authentication, or review the plugin code to verify if the AJAX handler lacks a capability check like 'manage_options'
    Affected if The AJAX action is registered without a capability check or is accessible to authenticated users with Subscriber role

If the plugin is installed at version 1.8.20 or lower, the vulnerable pprh_update_hints AJAX action exists, and Subscriber-level users can access the site, the environment is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest patched version (1.8.21 or higher). If no patch is available, disable the plugin immediately or restrict AJAX functionality via firewall rules until a fix is deployed.

Recommended fix High confidence

Version 1.8.21 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Pre* Party Resource Hints' plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, manually download the updated plugin from the WordPress plugin repository and reinstall
  6. After updating, verify the plugin version is 1.8.21 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4087 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4087 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data