LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38139: WordPress RD Station plugin <= 5.2.0 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities

Multiple Cross-Site Request Forgery (CSRF) vulnerabilities in RD Station plugin <= 5.2.0 at WordPress.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects WordPress sites using the RD Station plugin versions described as <=5.2.0. It is a CSRF flaw: an attacker would need to trick an authenticated user into taking an unwanted action. The reported impact is limited integrity and availability, not data theft. Business urgency is moderate, focused on confirming plugin use and vendor-supported remediation.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It does not have confirmed active exploitation in the provided sources, but exposed marketing sites can carry brand and operational risk if plugin actions are abused.

Technical view

CVE-2022-38139 is listed as multiple CWE-352 CSRF vulnerabilities in the RD Station WordPress plugin. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L, score 5.4. The source bundle does not identify specific endpoints, required WordPress roles, or a fixed version.

Likely exposure

Exposure is limited to WordPress environments where the RD Station plugin is installed at an affected version. The bundle states <=5.2.0, while the Patchstack URL text references <=5.1.3, so version validation should use authoritative vendor guidance.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires user interaction, consistent with CSRF, and could affect integrity or availability if a logged-in user is induced to trigger a vulnerable action.

Researcher notes

Evidence is sparse. The CVE identifies multiple CSRF issues and CVSS impact, but the bundle does not provide endpoint details, exploit prerequisites beyond UI:R, patch commit, or fixed-version confirmation. Avoid assuming affected roles or exploitability beyond the published vector.

Mitigation direction

  • Inventory WordPress sites for the RD Station plugin and installed version.
  • Check RD Station, WordPress.org, and Patchstack guidance for the fixed or unaffected version.
  • Update to a vendor-supported non-affected release if one is available.
  • Disable or remove the plugin where it is not business-critical.
  • Prioritize admin awareness and session hygiene until remediation is confirmed.

Validation and detection

  • Confirm whether RD Station plugin is present on each WordPress site.
  • Record exact plugin version and compare against vendor or Patchstack guidance.
  • Review WordPress audit logs for unexpected RD Station configuration changes.
  • Verify remediation by confirming the plugin is removed or updated.
  • Track the version discrepancy between bundle title and Patchstack reference.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-38139 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-38139Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
RD StationRD Station (WordPress plugin)n/aunaffected
Weakness

CWE details

CWE-352

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.