dbcve.org
Make Paths RelativeWordPress extension · Yasglobal

CVE-2023-27433

HIGH · 8.8 CVSS v3.1 Published 2023-10-04
Fix available
A fix is available. Upgrade to after 1.3.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in YAS Global Team Make Paths Relative allows Cross Site Request Forgery.This issue affects Make Paths Relative: from n/a through 1.3.0.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Make Paths Relative WordPress plugin. The plugin lacks proper anti-CSRF token/nonce validation, allowing attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or path configurations.

MitigationUpdate to a patched version of the plugin that implements proper nonce validation for all state-changing operations; alternatively, disable the plugin until a fix is available.

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
Make Paths RelativeWordPress extension
Affected:<= 1.3.0

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify plugin installation
    Check the wp-content/plugins/ directory for a folder named 'make-paths-relative' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'Make Paths Relative' by Yasglobal.
    Affected if plugin folder or entry exists in the WordPress plugins directory
  2. Identify installed version
    Open the main plugin PHP file (usually make-paths-relative.php) and locate the version header in the file comments, or check the plugin readme.txt file for the 'Stable tag' or 'Version' entry.
    Affected if version number displayed is 1.3.0 or lower
  3. Confirm plugin status
    In WordPress admin, go to Plugins > Installed Plugins and check if 'Make Paths Relative' shows as 'Active'. Alternatively, query the wp_options table for the option_name containing 'active_plugins'.
    Affected if plugin is currently activated on the WordPress site

A site is affected if the Make Paths Relative plugin by Yasglobal is installed, active, and running version 1.3.0 or lower, allowing CSRF attacks on authenticated administrators.

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.

From vendor data
Upgrade available Upgrade to a release after 1.3.0
Interim mitigation

Update to a patched version of the plugin that implements proper nonce validation for all state-changing operations; alternatively, disable the plugin until a fix is available.

Fix this in Make Paths Relative Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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