What is the CVSS score of EUVD-2026-53034?

EUVD-2026-53034 has a CVSS 3.1 base score of 4.9 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.3%.

PrettyLinks Plugin EUVD-2026-53034

| CVE-2026-5062 MEDIUM

SQL Injection (CWE-89)

2026-08-05 Wordfence

GHSA-r28m-4r72-h337

WordPress SQLi Wordpress Plugin Prettylinks Affiliate Link Management Url Shortener Link Cloaking Tracking Branded Short Links

4.9

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

4.9 MEDIUM

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

vuln.today AI

4.9 MEDIUM

Administrator authentication required (PR:H); browser-based admin page access (AV:N); read-only SQLi yields confidentiality loss only (C:H, I:N, A:N); no scope change.

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

4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Aug 05, 2026 - 05:59 vuln.today

CVE Published

Aug 05, 2026 - 05:27 cve.org

MEDIUM 4.9

DescriptionCVE.org

The PrettyLinks - Affiliate Links, Link Branding, Link Tracking, Marketing and Stripe Payments Plugin plugin for WordPress is vulnerable to SQL Injection via the 's' (search) parameter on the Pretty Links listing page in all versions up to, and including, 3.6.20. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query in the search_links_table() function. This makes it possible for authenticated attackers, with Administrator-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 PrettyLinks WordPress plugin (all versions through 3.6.20) enables authenticated administrators to extract arbitrary data from the underlying WordPress database by appending malicious SQL to the 's' search parameter on the Pretty Links listing page. The root cause is insufficient input escaping and absent prepared-statement usage in the search_links_table() function within PrliLinksController.php. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the CVSS confidentiality impact is rated High, meaning successful exploitation could expose all data stored in the WordPress database.

Technical ContextAI

PrettyLinks is a WordPress affiliate link management, URL shortening, and tracking plugin published by Supercleanse (CPE: cpe:2.3:a:supercleanse:prettylinks_-_affiliate_link_management,_url_shortener,_link_cloaking,_tracking_&_branded_short_links:*:*:*:*:*:*:*:*). The flaw is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command). Specifically, the search_links_table() function in app/controllers/PrliLinksController.php at lines 1047 and 1051 passes the raw user-supplied s parameter directly into a SQL query without escaping or binding it as a prepared statement parameter. WordPress plugins are expected to use $wpdb->prepare() or equivalent sanitization before interpolating input into queries against the MySQL/MariaDB backend; the absence of this practice here is the root cause. The affected functionality is the search input on the Pretty Links admin listing page, making it reachable only through the WordPress admin dashboard.

RemediationAI

A patch has been committed to the PrettyLinks plugin trunk repository (changeset 3493031 versus old 3444399, viewable at https://plugins.trac.wordpress.org/changeset?reponame=&new=3493031%40pretty-link%2Ftrunk&old=3444399%40pretty-link%2Ftrunk); however, the exact released patched version number is not independently confirmed from the available data - administrators should update to the latest available version of PrettyLinks via the WordPress plugin dashboard and verify the installed version exceeds 3.6.20. As a compensating control prior to patching, restrict WordPress Administrator role assignments to the minimum necessary personnel, as exploitation is entirely gated on administrator authentication. Enabling two-factor authentication on all WordPress administrator accounts reduces the risk that a credential compromise leads to exploitation. In managed or multisite WordPress environments, review whether any third-party administrators or agency accounts hold unnecessary admin-level access, and consider temporarily disabling the PrettyLinks search functionality via a WAF rule blocking requests to the Pretty Links listing page with a non-empty s parameter if immediate patching is not feasible.