LiveActive security incident?Get immediate response
CVE Record

CVE-2021-31867: Pimcore Customer Data Framework 'SegmentAssignmentController.php' Blind SQL Injection

Pimcore Customer Data Framework version 3.0.0 and earlier suffers from a Boolean-based blind SQL injection issue in the $id parameter of the SegmentAssignmentController.php component of the application. This issue was fixed in version 3.0.2 of the product.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw lets a highly privileged user abuse Pimcore Customer Data Framework to read or change database information through blind SQL injection. It is not described as remotely exploitable by anonymous users, but it can affect sensitive customer data if privileged access is compromised or misused.

Executive priority

Treat as a scheduled but important remediation for affected customer-data systems. Prioritize faster if privileged accounts are broadly shared, exposed through VPN weaknesses, or connected to high-value customer datasets.

Technical view

CVE-2021-31867 is CWE-89 Boolean-based blind SQL injection in the $id parameter of SegmentAssignmentController.php in Pimcore Customer Data Framework 3.0.0 and earlier. CVSS 3.1 is 6.5: network reachable, low complexity, high privileges required, no user interaction, high confidentiality and integrity impact.

Likely exposure

Exposure is likely limited to organizations running Pimcore Customer Data Framework 3.0.0 or earlier, especially where privileged application access exists outside tightly controlled administrative networks.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked KEV. The privilege requirement lowers broad internet risk, but successful abuse could still expose or alter important customer data.

Researcher notes

Evidence identifies the vulnerable component, parameter, weakness class, CVSS vector, and fixed version. The bundle does not include exploit telemetry, detailed patch diff, or deployment-specific attack paths, so validation should stay version- and exposure-focused.

Mitigation direction

  • Upgrade Pimcore Customer Data Framework to version 3.0.2 or later.
  • Identify and retire any 3.0.0 or earlier installations.
  • Restrict privileged Pimcore access to trusted users and networks.
  • Review vendor guidance before applying compensating controls.

Validation and detection

  • Inventory Pimcore Customer Data Framework versions across production and staging.
  • Confirm SegmentAssignmentController.php is from a fixed release.
  • Review privileged account access paths for unnecessary exposure.
  • Check application and database logs for unusual privileged data access.
Prepared
Confidence
high
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-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-31867 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:H/UI:N/S:U/C:H/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:H/UI:N/S:U/C:H/I:H/A:N1.25.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
PimcorePimcore Customer Data Framework3.0.0Listed
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.