Rapid Cache <= 1.2.3 — Unauthenticated Cache Poisoning

Am I affected?

• Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Rapid Cache.
• No admin access? Run a passive check of your site. It reads public files only.
• No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

1. No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
3. Watch Rapid Cache to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Joshua Provoste.

The Rapid Cache plugin for WordPress is vulnerable to Cache Poisoning in all versions up to, and including, 1.2.3. This is due to plugin storing HTTP headers in the cached data. This makes it possible for unauthenticated attackers to poison the cache with custom HTTP headers that may be unsanitized which can lead to Cross-Site Scripting.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

• Advisorywordfence.com

Timeline

1. Feb 17, 2025

   CVE published

   Severity high, CVSS 7.2

2. Nov 13, 2026

   Record last updated