dbcve.org
RankieWordPress extension · Valvepress

CVE-2025-39493

HIGH · 8.8 CVSS v3.1 Published 2025-05-16
Fix available
A fix is available. Upgrade to 1.8.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in ValvePress Rankie valvepress-rankie allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Rankie: from n/a through < 1.8.2.

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

A Missing Authorization vulnerability in the ValvePress Rankie WordPress plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized administrative actions or access to sensitive functionality that should be restricted to authenticated users.

MitigationUpgrade the Rankie plugin to version 1.8.2 or later to apply the authorization fix. Ensure proper access controls are in place and review user roles/permissions after updating.

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
RankieWordPress extension
Affected:< 1.8.2

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Confirm Rankie plugin is installed
    Check your WordPress installation for the Rankie plugin in wp-content/plugins/ folder or via WordPress admin dashboard under Plugins > Installed Plugins
    Affected if The Rankie plugin by ValvePress is present in the WordPress installation
  2. Identify installed Rankie version
    Open the main Rankie plugin file (usually rankie.php) and locate the version in the plugin header comment, or check the WordPress admin Plugins page where version numbers are displayed
    Affected if Unable to determine version or version is displayed in the plugin list
  3. Compare version against vulnerable range
    Compare your installed version number to the affected range: versions before 1.8.2 are vulnerable
    Affected if Installed version is lower than 1.8.2 (e.g., 1.8.1, 1.8.0, 1.7.x, etc.)
  4. Verify authorization controls are bypassed
    Since this is a missing authorization vulnerability, review if unauthenticated or low-privilege users can access admin functionality meant for higher roles. Check server access logs for unusual requests to Rankie-related endpoints
    Affected if Unauthenticated or subscriber-level users can access admin actions or sensitive plugin features without proper permission

You are affected if the Rankie plugin is installed with a version lower than 1.8.2 and unauthorized users can bypass access controls to reach restricted functionality.

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 1.8.2 or later
Fixed in 1.8.2
Interim mitigation

Upgrade the Rankie plugin to version 1.8.2 or later to apply the authorization fix. Ensure proper access controls are in place and review user roles/permissions after updating.

Recommended fix Moderate confidence

Rankie 1.8.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Rankie plugin in the list
  4. If an update is available, click 'Update Now' to upgrade to version 1.8.2
  5. Alternatively, go to Plugins > Add New > Upload to manually upload the latest version from the WordPress plugin repository
  6. After updating, verify the plugin version shows 1.8.2 or higher
  7. Review user roles and permissions to ensure only authorized administrators have access to Rankie settings

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

Fix this in Rankie Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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