dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-31288

HIGH · 7.2 CVSS v3.1 Published 2024-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
Server-Side Request Forgery (SSRF) vulnerability in RapidLoad RapidLoad Power-Up for Autoptimize.This issue affects RapidLoad Power-Up for Autoptimize: from n/a through 2.2.11.

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

Server-Side Request Forgery (SSRF) vulnerability in the RapidLoad Power-Up for Autoptimize WordPress plugin (versions up to 2.2.11). The vulnerability allows attackers to make the server perform unintended requests to arbitrary URLs, potentially accessing internal services, cloud metadata endpoints, or internal network resources.

MitigationUpdate to the latest version of RapidLoad Power-Up for Autoptimize when a patched release becomes available. Until then, restrict access to the plugin administrative interfaces and monitor for suspicious outbound requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm plugin installation
    Navigate to WordPress admin > Plugins and check if 'RapidLoad Power-Up for Autoptimize' is installed and active, or inspect the plugins directory at /wp-content/plugins/ for a folder starting with 'rapidload'
    Affected if The plugin is installed and active on the WordPress site
  2. Identify installed version
    In WordPress admin > Plugins, click on the plugin details to view the installed version number, or read the main plugin file (usually rapidload.php) and look for the 'Version' header in the plugin comments
    Affected if The version is 2.2.11 or lower, or if the version cannot be determined but the plugin is present
  3. Check for exposed API endpoints
    Probe the site for RapidLoad AJAX endpoints - typically at /wp-admin/admin-ajax.php?action=uni_rocket or similar RapidLoad-related actions. Use a tool like Burp Suite or curl to send a request with an arbitrary URL parameter (e.g., &url=http://169.254.169.254/)
    Affected if The endpoint responds and appears to accept arbitrary URL parameters without proper validation
  4. Review access controls
    Check WordPress user roles and capabilities - determine if unauthenticated or low-privilege users can access RapidLoad features. Inspect the plugin settings in WordPress admin under RapidLoad options
    Affected if Non-admin users or unauthenticated visitors can trigger the plugin's request-making functionality
  5. Monitor outbound requests
    Review server access logs (Apache/nginx) for suspicious outbound requests originating from the web server, particularly to internal IPs (10.x.x.x, 172.16-31.x.x, 192.168.x.x), cloud metadata endpoints (169.254.169.254), or unusual external domains
    Affected if The server has made or attempted requests to internal or unexpected external URLs that were not initiated by legitimate admin actions

A user is affected if the RapidLoad Power-Up for Autoptimize plugin is installed with version 2.2.11 or lower and the plugin's API endpoints are accessible to users who should not have that capability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of RapidLoad Power-Up for Autoptimize when a patched release becomes available. Until then, restrict access to the plugin administrative interfaces and monitor for suspicious outbound requests.

Recommended fix Moderate confidence

Version 2.2.12 or later (any version higher than 2.2.11)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Locate 'RapidLoad Power-Up for Autoptimize' plugin
  4. 4. Check the current installed version (should be 2.2.11 or lower if vulnerable)
  5. 5. Update the plugin to the latest available version from the WordPress plugin repository
  6. 6. Verify the update was successful by confirming the new version number
Caveat Review plugin settings after upgrade as minor configuration adjustments may be needed

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

Have this fixed 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 help mitigating

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-2024-31288 — 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-31288 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