Summary
CVE-2026-87767 is an unauthenticated SQL Injection (CWE-89) vulnerability in the "wp shortcut link and advertisement baner" WordPress plugin, affecting all versions up to and including 1.2.0. The plugin fails to sanitize and escape the url parameter before using it in a SQL query executed by an AJAX action that is accessible without authentication. This allows any remote, unauthenticated attacker to inject arbitrary SQL and extract sensitive data from the WordPress database, and the flaw carries a High CVSS v3.1 base score of 8.6.
Technical details
- Root cause: The plugin’s AJAX handler builds a SQL query using the
urlparameter without proper sanitization or escaping, permitting attacker-controlled SQL syntax to be executed against the database. - Trigger conditions: The vulnerable AJAX action is registered for unauthenticated (
nopriv) access, so no login, session, or user interaction is required to reach the vulnerable code path. - Attack vector: Network-based; an attacker sends a crafted HTTP request containing a malicious
urlparameter to the plugin’s AJAX endpoint. - Impact: Successful exploitation allows extraction of sensitive database contents (high confidentiality impact), such as user credentials, session tokens, or other stored data. The vulnerability does not directly affect data integrity or availability (I:N/A:N).
Affected software
- WP Shortcut Link and Advertisement Baner (WordPress plugin) — all versions through 1.2.0 (<= 1.2.0)
Severity
- CVSS v3.1 Base Score: 8.6 (High)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Mitigation and recommended actions
- Immediate: As of publication, no patched version of the plugin has been released. Sites running any version up to and including 1.2.0 remain vulnerable.
- If no patch is available:
- Deactivate and remove the "wp shortcut link and advertisement baner" plugin until a fixed version is released.
- If removal is not immediately feasible, block or restrict access to the plugin’s AJAX endpoint (
admin-ajax.phprequests referencing this plugin’s action) at the web server or WAF layer. - Deploy a Web Application Firewall (WAF) with SQL injection detection rules as a compensating control.
- Monitor web server and database logs for anomalous requests containing SQL metacharacters in the
urlparameter. - Rotate credentials and audit the database for signs of unauthorized access if compromise is suspected.

