LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36012: Magento Commerce Gift Card Business Logic Error

Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by a business logic error in the placeOrder graphql mutation. An authenticated attacker can leverage this vulnerability to altar the price of an item.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw let a logged-in Magento Commerce user manipulate item pricing during checkout through a GraphQL order operation. For an online store, the business impact is transaction integrity: customers could potentially place orders at prices the business did not intend.

Executive priority

Treat this as a near-term e-commerce integrity risk rather than a broad system takeover issue. Prioritize stores processing live payments or gift cards, because successful abuse could directly affect revenue, order accuracy, and customer trust.

Technical view

CVE-2021-36012 is a CWE-840 business logic error in the Magento Commerce placeOrder GraphQL mutation. A network attacker with low privileges and no user interaction could alter an item price. The CVSS 3.1 score is 6.5, with high integrity impact and no confidentiality or availability impact stated.

Likely exposure

Exposure is most relevant to internet-facing Magento Commerce stores running 2.4.2, 2.4.2-p1, 2.3.7, or earlier versions as listed in the CVE source bundle, especially where authenticated customer checkout and GraphQL order placement are enabled.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as CISA KEV in the bundle. Exploitation requires authentication but not user interaction, so normal customer account access may be enough for abuse if the store is vulnerable.

Researcher notes

Evidence is limited to the CVE record and Adobe advisory reference in the bundle. The vulnerability is described at a high level only; no public exploit status, detailed patch version, or proof-of-concept information is provided here.

Mitigation direction

  • Confirm Magento Commerce version and compare it with Adobe APSB21-64 guidance.
  • Apply the relevant vendor security update or supported upgrade for your Magento branch.
  • Review recent orders for unexpected price changes, discounts, or gift card anomalies.
  • Monitor authenticated checkout and GraphQL order activity until remediation is complete.
  • Retest checkout pricing logic after patching in staging and production.

Validation and detection

  • Inventory all Magento Commerce instances, including staging and secondary storefronts.
  • Check whether affected versions 2.4.2, 2.4.2-p1, 2.3.7, or earlier are present.
  • Confirm GraphQL checkout paths are enabled and reachable by authenticated users.
  • Review order records for mismatches between catalog price, cart price, and final order price.
  • Verify vendor update status against Adobe APSB21-64 documentation.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-840: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-36012 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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
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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-36012Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AdobeMagento Commerceunspecified, unspecified, unspecified, unspecifiedListed
Weakness

CWE details

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

CWE-840 · source CWE mapping

Business Logic Errors

Business Logic Errors represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.