dbcve.org
Rd StationWordPress extension · Rdstation

CVE-2024-6894

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-05
Fix available
A fix is available. Upgrade to 5.4.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The RD Station plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 5.3.2 due to insufficient input sanitization and output escaping of post metaboxes added by the plugin. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · high confidence

The RD Station WordPress plugin fails to sanitize and escape user input in post metaboxes, allowing authenticated Contributors+ to inject malicious JavaScript that executes when other users view affected pages. This stored XSS affects all pages where the plugin's metaboxes are rendered.

MitigationUpdate the plugin to version 5.3.3 or later which includes proper input sanitization and output escaping. Until then, restrict Contributor-level user creation and monitor for suspicious script injections in page content.

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
Rd StationWordPress extension
Affected:< 5.4.0

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 RD Station plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Rd Station' or 'RD Station' in the list. Note the version number displayed below the plugin name.
    Affected if The plugin is installed with a version lower than 5.4.0
  2. Verify Contributor user role exists
    In WordPress admin, go to Users > Users List and check if any users have the 'Contributor' role assigned.
    Affected if At least one user with Contributor role exists and the plugin is installed with version < 5.4.0
  3. Check if plugin metaboxes render on posts/pages
    Open a post or page editor in the WordPress admin. Look for an RD Station metabox in the sidebar or below the editor content. This metabox is typically labeled with RD Station branding.
    Affected if The RD Station metabox is visible and the plugin version is < 5.4.0
  4. Inspect post content for suspicious script injections
    View the source code of published pages or use a database query to search posts table for <script> tags, javascript: URLs, or onload/onerror event handlers in custom fields or postmeta.
    Affected if Malicious script tags or event handlers are found in post content and the plugin version is < 5.4.0

You are affected if the RD Station plugin is installed with a version below 5.4.0 and Contributor-level users can access the WordPress admin where the plugin metaboxes render on posts or pages.

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 5.4.0 or later
Fixed in 5.4.0
Interim mitigation

Update the plugin to version 5.3.3 or later which includes proper input sanitization and output escaping. Until then, restrict Contributor-level user creation and monitor for suspicious script injections in page content.

Recommended fix High confidence

5.4.0

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the RD Station plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to version 5.4.0
  5. 5. Alternatively, download RD Station version 5.4.0 from the WordPress plugin repository
  6. 6. Deactivate the current version, then upload and install version 5.4.0
  7. 7. Reactivate the plugin after installation
  8. 8. Verify the plugin shows version 5.4.0 under Plugins > Installed Plugins

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

Fix this in Rd Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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