CVE-2026-28044
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Media WP Rocket allows Stored XSS.This issue affects WP Rocket: from n/a through 3.19.4.
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 confidenceA Stored Cross-Site Scripting (XSS) vulnerability exists in the WP Rocket WordPress plugin versions up to 3.19.4. The plugin fails to properly sanitize and escape user-supplied input before storing it and rendering it within web pages, allowing an attacker to inject malicious JavaScript code that executes in the browsers of other users who view the affected content.
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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Rocket plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Rocket' in the list, or check the /wp-content/plugins/rocket-footer-js directory existsAffected if WP Rocket plugin is present on the WordPress site
-
Check installed WP Rocket versionNavigate to WP Rocket > Dashboard in the admin panel and locate the version number displayed, or check the main plugin file header in /wp-content/plugins/rocket-footer-js/rocket-footer-js.phpAffected if Version is 3.19.4 or lower (vulnerable); version is 3.19.5 or higher (patched)
-
Identify if plugin settings are accessible to untrusted usersReview WordPress user roles with access to WP Rocket settings (Settings > WP Rocket) and check if any role below Administrator can modify plugin optionsAffected if Users with Editor, Author, or Contributor roles can access and modify plugin settings - combined with vulnerable version, this enables stored XSS injection
You are affected if WP Rocket version 3.19.4 or lower is installed and the plugin settings are accessible to users who can add or modify plugin options.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade WP Rocket to the latest version (3.19.5 or later) which includes proper input sanitization and output encoding to prevent XSS attacks. Until patched, restrict administrative access and validate all user inputs in the plugin settings.
Latest WP Rocket version (after 3.19.4)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate WP Rocket in the plugin list
- 4. If an update is available, click 'Update Now' to update WP Rocket to the latest version
- 5. Alternatively, download the latest WP Rocket version from the official WordPress repository or your WP Rocket account
- 6. Deactivate and delete the current WP Rocket plugin, then upload and activate the new version
- 7. Clear all site caches after updating to ensure changes take effect
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28044 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28044 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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