CVE-2024-13789 CRITICAL

CVE-2024-13789: Ravpage <= 2.31 - PHP Object Injection

Vendor Matiskiba
Product ravpage
Weakness CWE-502 · Unsafe deserialization
Published February 20, 2025
Last update April 8, 2026

CVSS base score

9.8/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity High

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

RavPage versions 2.31 and earlier contain a deserialization vulnerability that allows unauthenticated attackers to execute arbitrary code on the server. The vulnerability exists because the application deserializes untrusted data without proper validation. An attacker can exploit this remotely over the network without requiring user interaction or authentication.

What an attacker can do

03Attacker Capabilities

Run their own code on the server and take full control of the site.

Potential impact on your site

04Site Impact

Complete compromise of the site and server; attacker can read, modify, or delete all data and install backdoors.

Conditions required to exploit

05Prerequisites

Network access to the vulnerable RavPage installation; no authentication or user interaction required.

Key dates

06Disclosure timeline

February 20, 2025 CVE published
April 8, 2026 Record updated