dbcve.org
Rd StationWordPress extension · Rdstation

CVE-2022-38139

HIGH · 8.8 CVSS v3.1 Published 2022-09-13
Fix available
A fix is available. Upgrade to after 5.2.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Multiple Cross-Site Request Forgery (CSRF) vulnerabilities in RD Station plugin <= 5.2.0 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

Multiple Cross-Site Request Forgery (CSRF) vulnerabilities exist in the RD Station WordPress plugin version 5.2.0 and below. Attackers can exploit missing or improper CSRF token validation to trick authenticated administrators into performing unintended actions such as modifying plugin settings or exfiltrating data.

MitigationUpdate the RD Station plugin to a version newer than 5.2.0 which should contain proper anti-CSRF token implementations. Alternatively, implement nonce verification on all form submissions and AJAX actions within the plugin.

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.2.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 RD Station plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Rd Station' or 'RD Station' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list, regardless of activation status.
  2. Identify installed plugin version
    In the Plugins list, locate the RD Station plugin entry. The version number is displayed below the plugin name. Alternatively, access via Plugins > Plugin Editor if file access is available.
    Affected if The version listed is 5.2.0 or any version lower than 5.2.0.
  3. Verify plugin handles form submissions or AJAX requests
    Examine the plugin files for form tags in admin settings pages or AJAX action handlers. Look for files in the plugin directory containing form elements or wp_ajax_ hooks.
    Affected if The plugin contains admin settings forms or AJAX handlers that process user-submitted data without explicit mention of nonce or CSRF token verification in the code.
  4. Check for CSRF token implementation in plugin code
    If plugin file access is available, search plugin PHP files for occurrences of 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' within form handling and AJAX callback functions.
    Affected if Form processing or AJAX action handlers lack nonce verification calls, indicating missing CSRF protection.

A user is affected if the RD Station plugin version is 5.2.0 or lower and the plugin contains admin forms or AJAX actions without CSRF token validation.

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 5.2.0
Interim mitigation

Update the RD Station plugin to a version newer than 5.2.0 which should contain proper anti-CSRF token implementations. Alternatively, implement nonce verification on all form submissions and AJAX actions within the plugin.

Recommended fix Moderate confidence

Update RD Station plugin to a version higher than 5.2.0 (check WordPress plugin repository for the latest fixed release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the RD Station plugin
  4. Check if the current version is 5.2.0 or earlier
  5. If vulnerable, click 'Update Now' to update to the latest available version
  6. Alternatively, download the latest version from the WordPress plugin repository and upload it manually

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

Fix this in Rd Station Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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