dbcve.org
RavpageWordPress extension · Ravpage Project

CVE-2022-29415

MEDIUM · 6.1 CVSS v3.1 Published 2022-04-28
Fix available
A fix is available. Upgrade to after 2.16 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Unauthenticated Reflected Cross-Site Scripting (XSS) vulnerability in Mati Skiba @ Rav Messer's Ravpage plugin <= 2.16 at WordPress.

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 reflected Cross-Site Scripting (XSS) vulnerability exists in the Ravpage WordPress plugin (versions 2.16 and below) by Mati Skiba @ Rav Messer. The vulnerability is unauthenticated, meaning attackers do not need credentials to exploit it. Reflected XSS occurs when user-supplied input is immediately returned by a web application in an error message, search result, or any other response that includes some or all of the input provided by the user, without that data being rendered safe.

MitigationUpdate the Ravpage plugin to a version newer than 2.16. If no update is available, remove or disable the plugin until a patch is released. Alternatively, implement WAF rules to block XSS attack patterns in requests targeting the affected endpoint.

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.16

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify if Ravpage plugin is installed
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Ravpage' or 'Ravpage Project Ravpage' in the list of installed plugins. Alternatively, check the /wp-content/plugins/ directory for a folder named 'ravpage'.
    Affected if The Ravpage plugin folder exists in the WordPress plugins directory.
  2. Determine installed Ravpage version
    In the WordPress admin under Plugins > Installed Plugins, find the Ravpage entry and read the version number displayed beneath the plugin name. If the plugin files are accessible, also check the main PHP file for a 'Version' header in the plugin comments.
    Affected if The installed version is 2.16 or lower.
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify whether Ravpage shows as 'Active' (not just installed). An inactive plugin may not be directly exploitable.
    Affected if Ravpage is both installed and actively enabled on the WordPress site.
  4. Check server access logs for XSS attack patterns
    Review web server access logs (Apache, Nginx, or WAF logs) for requests to any Ravpage-related URLs containing suspicious patterns like <script>, javascript:, onerror=, or other HTML/script tags in query parameters.
    Affected if Suspicious XSS payloads appear in recent access logs targeting Ravpage endpoints.

A WordPress site is affected if it has Ravpage plugin installed, enabled, and running version 2.16 or lower.

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 a release after 2.16
Interim mitigation

Update the Ravpage plugin to a version newer than 2.16. If no update is available, remove or disable the plugin until a patch is released. Alternatively, implement WAF rules to block XSS attack patterns in requests targeting the affected endpoint.

Recommended fix Moderate confidence

Latest available version of Ravpage in the WordPress plugin repository (beyond 2.16)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Ravpage plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, navigate to Dashboard > Updates and apply all available updates
  6. 6. After updating, verify the plugin version has changed to confirm the update was applied

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

Fix this in Ravpage Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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