dbcve.org
Yet Another Related Posts PluginWordPress extension · Yarpp

CVE-2022-45374

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 5.30.5 or later.
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in YARPP allows PHP Local File Inclusion.This issue affects YARPP: from n/a through 5.30.4.

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

YARPP plugin versions up to 5.30.4 contain a path traversal vulnerability allowing PHP Local File Inclusion. The improper limitation of pathnames to restricted directories enables attackers to manipulate file path references (e.g., using ../ sequences) to access or include sensitive PHP files outside the intended directory boundaries.

MitigationUpgrade YARPP to the latest version which patches the path traversal input validation. If patching is not immediately possible, restrict file access permissions and validate all file path inputs to reject directory traversal sequences.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Yet Another Related Posts PluginWordPress extension
Affected:< 5.30.5

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 YARPP plugin installation and version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'YARPP' (Yet Another Related Posts Plugin) and note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/yet-another-related-posts-plugin/yet-another-related-posts-plugin.php
    Affected if The installed version is below 5.30.5 (e.g., 5.30.4, 5.30.3, etc.)
  2. Identify the template include functionality
    YARPP allows custom template files to be included via the 'template' parameter in WordPress. Locate the file that handles template loading in the YARPP plugin directory, typically in the core template loading routine that processes user-supplied template path requests
    Affected if The YARPP template loading mechanism processes a user-controllable template parameter without proper path sanitization
  3. Check for path traversal attempts in access logs
    Review web server access logs (Apache error.log, Nginx access.log, or WordPress debug logs) for requests containing '../' sequences targeting YARPP endpoints. Search for patterns like 'template=../' or 'yarpp_template=../../' in query parameters
    Affected if Log entries show '../' directory traversal sequences in YARPP-related requests, indicating exploitation attempts
  4. Inspect for unauthorized file inclusions
    Check the wp-content directory and other sensitive locations (e.g., wp-config.php) for any newly created or modified PHP files that may have been included via the path traversal vulnerability. Compare file hashes against known good backups
    Affected if Suspicious PHP files exist outside the intended YARPP templates directory, or known configuration files show unexpected modifications

A user is affected if YARPP version is below 5.30.5 AND the plugin template functionality is accessible to users who could supply malicious path traversal sequences.

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
Upgrade available Upgrade to 5.30.5 or later
Fixed in 5.30.5
Interim mitigation

Upgrade YARPP to the latest version which patches the path traversal input validation. If patching is not immediately possible, restrict file access permissions and validate all file path inputs to reject directory traversal sequences.

Recommended fix High confidence

5.30.5

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Yet Another Related Posts Plugin (YARPP)' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 5.30.5
  5. Alternatively, navigate to Dashboard > Updates and select YARPP to update
  6. Verify the update completed successfully by checking the plugin version

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

Fix this in Yet Another Related Posts Plugin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45374 — 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-2022-45374 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