LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4391: Ultimate Gift Cards for WooCommerce <= 2.1.1 - Cross-Site Request Forgery Bypass

The Ultimate Gift Cards for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.1.1. This is due to missing or incorrect nonce validation on the mwb_wgm_save_post() function. This makes it possible for unauthenticated attackers to modify product gift card details 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

This flaw lets an attacker trick a logged-in WordPress administrator into changing gift card product settings for a WooCommerce store. It requires administrator interaction, so it is not a self-running compromise, but it can affect store integrity and customer-facing gift card behavior.

Executive priority

Treat as a moderate e-commerce integrity issue. Remediate during the next maintenance window, sooner for stores with active gift card sales or many administrators.

Technical view

Ultimate Gift Cards for WooCommerce through 2.1.1 lacks proper nonce validation in mwb_wgm_save_post(), creating a CWE-352 CSRF issue. An unauthenticated attacker can cause an administrator’s browser to submit unauthorized product gift card detail changes. CVSS 3.1 is 4.3 with low integrity impact only.

Likely exposure

Exposure is limited to WordPress/WooCommerce sites running Ultimate Gift Cards for WooCommerce version 2.1.1 or earlier. Risk is higher where administrators remain logged into wp-admin while opening untrusted links or messages.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. Abuse requires social engineering a site administrator into performing an action such as clicking a link while authenticated.

Researcher notes

The strongest evidence is the CVE description and Wordfence/NinTechNet references. The affected metadata in the bundle is sparse, but the narrative identifies versions through 2.1.1 and a 2.1.2 source reference suggests the relevant code area.

Mitigation direction

  • Upgrade Ultimate Gift Cards for WooCommerce to a release newer than 2.1.1.
  • Confirm vendor guidance and plugin changelog before closing remediation.
  • Restrict administrator browsing from authenticated WordPress sessions.
  • Review gift card product settings for unauthorized changes.
  • Ensure administrators use separate browsers or profiles for wp-admin work.

Validation and detection

  • Inventory all WordPress sites for the plugin and exact version.
  • Confirm no installed instance is version 2.1.1 or earlier.
  • Review gift card product change history for unexpected edits.
  • Verify the save handler uses nonce validation after updating.
  • Check whether affected administrators reported suspicious links or prompts.
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-4391 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-4391Attack 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
wpswingsUltimate Gift Cards for WooCommerce0unaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.