LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23405: SQL Injection

This affects the package pimcore/pimcore before 10.0.7. This issue exists due to the absence of check on the storeId parameter in the method collectionsActionGet and groupsActionGet method within the ClassificationstoreController class.

HighCVSS 8.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-23405 is a high-severity SQL injection in pimcore/pimcore before 10.0.7. A logged-in attacker could abuse unchecked storeId handling in classification store requests, potentially exposing or changing database data and causing limited availability impact.

Executive priority

Prioritize remediation for internet-facing or broadly accessible Pimcore environments. The business risk is unauthorized database access or modification by a low-privileged authenticated user, with a published fix boundary at 10.0.7.

Technical view

The issue is missing validation of the storeId parameter in collectionsActionGet and groupsActionGet within Pimcore's ClassificationstoreController. The supplied CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L, indicating network reachability, low complexity, required low privileges, and high confidentiality and integrity impact.

Likely exposure

Exposure is most likely in Pimcore installations running pimcore/pimcore before 10.0.7 where authenticated users can reach the affected classification store controller functionality.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Snyk lists exploit maturity as functional, so treat exploitation as plausible for exposed, vulnerable deployments, but do not claim active attacks from these sources.

Researcher notes

Focus review on storeId handling in ClassificationstoreController methods collectionsActionGet and groupsActionGet. The available evidence identifies the vulnerable parameter and fixed version boundary, but does not provide CPEs, affected configuration details, or confirmed exploitation telemetry.

Mitigation direction

  • Inventory Pimcore deployments and identify versions before 10.0.7.
  • Upgrade pimcore/pimcore to 10.0.7 or later.
  • Restrict affected Pimcore functions to trusted authenticated users.
  • Review Pimcore and Snyk guidance for backports or compensating controls.

Validation and detection

  • Confirm the installed pimcore/pimcore version is 10.0.7 or later.
  • Check dependency lockfiles and deployed artifacts, not only source manifests.
  • Review logs for suspicious classification store requests by authenticated users.
  • Verify access controls around classification store administration paths.
Prepared
Confidence
high
Sources
4

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.

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-23405 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
High
CVSS
8.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L/E:F/RL:O/RC:C

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
3Source 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
8.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L/E:F/RL:O/RC:C2.85.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.3High
CVSS 3.1 vector shape for CVE-2021-23405Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L/E:F/RL:O/RC:C

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
n/apimcore/pimcoreunspecifiedListed
Weakness

CWE details

No CWE listed

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