dbcve.org
RavpageWordPress extension · Matiskiba

CVE-2024-13789

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-20
Fix available
A fix is available. Upgrade to after 2.31 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The ravpage plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.31 via deserialization of untrusted input from the 'paramsv2' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

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

The ravpage WordPress plugin versions up to 2.31 is vulnerable to PHP Object Injection via deserialization of untrusted input from the 'paramsv2' parameter. This allows unauthenticated attackers to inject arbitrary PHP objects. While no POP chain exists in the plugin itself, exploitation becomes critical when other installed plugins or themes contain POP chains, potentially allowing arbitrary file deletion, data exfiltration, or code execution.

MitigationUpdate the ravpage plugin to the latest version once a patch is released, or remove the plugin if unused. Audit all other installed plugins and themes for PHP Object Injection vulnerabilities and POP chains as the primary attack vector.

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
RavpageWordPress extension
Affected:<= 2.31

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

CVSS:3.1/AV:N/AC:L/PR:N/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 ravpage plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate 'Ravpage' by Matiskiba, and record the version number displayed. Alternatively, check the plugin's main PHP file header for the Version comment, or use WP-CLI: wp plugin list --name=ravpage --format=table
    Affected if The plugin is installed and the version shown is 2.31 or lower (any version up to and including 2.31)
  2. Verify the plugin is active
    In the WordPress Plugins admin page, confirm the Ravpage plugin shows as 'Active'. If using WP-CLI: wp plugin is-active ravpage
    Affected if The ravpage plugin is currently activated on the WordPress site
  3. Identify exposed endpoints handling the paramsv2 parameter
    Review the plugin's PHP files for code that processes the 'paramsv2' parameter, typically using unserialize() on $_POST, $_GET, or $_REQUEST data. Search plugin files for 'paramsv2' and 'unserialize'. Use web server access logs to check for requests containing 'paramsv2' parameter: grep -i 'paramsv2' /var/log/apache2/access.log (or equivalent log path)
    Affected if The plugin processes the paramsv2 parameter via deserialization and this parameter is accessible from the web (endpoints are publicly reachable)
  4. Check for exploitation indicators in logs
    Search application and web server logs for suspicious patterns indicating PHP Object Injection attempts, such as serialized PHP objects (O:, C:, a:) in paramsv2 values, or known POP chain class names. Example: grep -E 'paramsv2.*(O:|C:|a:)' /var/log/apache2/access.log
    Affected if There are log entries showing serialized PHP objects or known exploitation patterns being passed through the paramsv2 parameter

Your environment is affected if the ravpage plugin version is 2.31 or lower, the plugin is active, and the paramsv2 parameter handling is exposed and processes untrusted deserialized input.

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 2.31
Interim mitigation

Update the ravpage plugin to the latest version once a patch is released, or remove the plugin if unused. Audit all other installed plugins and themes for PHP Object Injection vulnerabilities and POP chains as the primary attack vector.

Fix this in Ravpage 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-2024-13789 — 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-2024-13789 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