Radar sectionsDatabase
Check my site
WordPress plugin

YARPP — Yet Another Related Posts Plugin <= 5.30.2 - Authenticated (Subscriber+) SQL Injection via Shortcode

CVE-2023-0579Published · Updated

Action summary

Affected: <5.30.3Update to 5.30.3 or newer

All remediation steps
Severity
High8.8
CVSS
8.8
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-89 SQL Injection
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

YARPP – Yet Another Related Posts Plugin yet-another-related-posts-plugin

  1. Affected< 5.30.3
  2. Patched in5.30.3

Update to 5.30.3 or newer.

You are affected if you run < 5.30.3. Version 5.30.3 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under YARPP – Yet Another Related Posts Plugin.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 5.30.3, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch YARPP – Yet Another Related Posts Plugin to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Erwan LR.

The YARRP plugin for WordPress is vulnerable to SQL Injection via the 'limit' parameter set via a shortcode in versions up to, and including, 5.30.2 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 permissions and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in YARPP – Yet Another Related Posts Plugin

All 8
More vulnerabilities in YARPP – Yet Another Related Posts Plugin
SeverityVulnerabilityCVEPublished
Medium5.3Missing Authorization
≤5.30.10Update to 5.30.11
CVE-2024-43919
Medium4.4Authenticated(Administrator+) Cross-Site Scripting
≤5.30.9Update to 5.30.10
CVE-2023-6495
Medium4.4Authenticated(Administrator+) Stored Cross-Site Scripting via settings
≤5.30.9Update to 5.30.10
CVE-2024-0602
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤5.30.3Update to 5.30.4
CVE-2023-2433
High8.8Authenticated (Subscriber+) Local File Inclusion
≤5.30.4Update to 5.30.5
CVE-2022-45374

Same weakness (SQL Injection)

All SQL Injection
Other SQL Injection vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 8.8

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?