LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4396: Rucy <= 0.4.4 - Cross-Site Request Forgery Bypass

The Rucy plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 0.4.4. This is due to missing or incorrect nonce validation on the save_rc_post_meta() function. This makes it possible for unauthenticated attackers to save post meta via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A malicious site or link could make a logged-in WordPress administrator unknowingly change Rucy-related post metadata. The sources do not describe server takeover or data theft, but unauthorized metadata changes can still affect site content behavior and integrity.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It needs timely remediation on sites using Rucy, especially where administrators manage high-value content, but the sources do not support emergency handling for active exploitation.

Technical view

Rucy for WordPress through version 0.4.4 lacks or incorrectly validates a nonce in save_rc_post_meta(), creating a CSRF issue. An unauthenticated attacker needs administrator interaction. CVSS 3.1 is 4.3 with low integrity impact and no stated confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites with the Rucy plugin installed at version 0.4.4 or earlier. Sites without Rucy, or with versions not covered by the source bundle, should not be assumed affected.

Exploitation context

The CVE is not listed as KEV, and the source bundle provides no evidence of active exploitation. Abuse requires tricking a logged-in administrator into taking an action, such as following a crafted link.

Researcher notes

Primary weakness is CWE-352 in save_rc_post_meta() nonce handling. The public bundle identifies affected versions through 0.4.4 and administrator interaction requirements, but it does not provide exploit status, payload details, or a definitive fixed version.

Mitigation direction

  • Inventory WordPress sites for the Rucy plugin and version.
  • Update Rucy if vendor guidance identifies a fixed release.
  • Disable or remove Rucy where it is unused or cannot be updated.
  • Limit administrator browsing while logged into WordPress.
  • Check vendor and Wordfence guidance before assuming remediation is complete.

Validation and detection

  • Confirm whether Rucy is installed on each WordPress site.
  • Verify installed Rucy versions are not 0.4.4 or earlier.
  • Review administrator-accessible workflows involving Rucy post metadata changes.
  • Check logs for unexpected post metadata changes around administrator sessions.
  • Document any compensating controls if the plugin remains installed.
Prepared
Confidence
medium
Sources
5

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-2021-4396 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
4.3 (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:N

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
10Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2021-4396Attack 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:N

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

Products and packages named in the record

VendorProductVersion / packageStatus
gips-nitaRucy0unaffected
Weakness

CWE details

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