LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3574: Improper Authorization in pimcore/customer-data-framework

Improper Authorization in GitHub repository pimcore/customer-data-framework prior to 3.4.1.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-3574 is an improper authorization issue in pimcore/customer-data-framework before version 3.4.1. A lower-privileged authenticated user could potentially access or affect customer-data-related functionality they should not be allowed to use. The business risk is unauthorized customer data exposure or changes in systems using this Pimcore component.

Executive priority

Treat this as a moderate-priority remediation for Pimcore environments handling customer data. Prioritize systems with many internal users, external customer portals, or sensitive customer records. It is not KEV-listed in the provided sources, but the data-access context warrants timely patching.

Technical view

The CVE describes CWE-285 improper authorization in the pimcore/customer-data-framework GitHub repository prior to 3.4.1. CVSS 3.0 is 6.3 with network access, low complexity, low privileges, no user interaction, and limited confidentiality, integrity, and availability impact. Public details in the bundle do not define exact vulnerable endpoints or exploit flow.

Likely exposure

Exposure is likely limited to deployments using pimcore/customer-data-framework versions earlier than 3.4.1, especially where authenticated users have access to customer data framework features. The bundle does not identify affected CPEs, deployment defaults, or specific public routes.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates an attacker needs low privileges but no user interaction, making internal account abuse or compromised-user scenarios more relevant than unauthenticated internet-scale exploitation.

Researcher notes

Evidence is sparse: the CVE identifies improper authorization before 3.4.1, CWE-285, CVSS 6.3, and a fixing commit reference. The bundle does not provide endpoint-level details, exploit indicators, or proof of exploitation. Validation should focus on version state and authorization behavior, not assumed exploit patterns.

Mitigation direction

  • Upgrade pimcore/customer-data-framework to version 3.4.1 or later.
  • Check Pimcore project guidance and release notes before production rollout.
  • Review roles allowed to access customer data framework functionality.
  • Restrict unnecessary authenticated access until upgraded.
  • Run application regression tests for authorization-sensitive customer data workflows.

Validation and detection

  • Inventory applications using pimcore/customer-data-framework and record installed versions.
  • Confirm no deployed instance is running a version earlier than 3.4.1.
  • Review customer data framework permissions for least-privilege alignment.
  • Check logs for unusual authenticated access to customer data features.
  • Verify authorization tests cover lower-privileged user behavior.
Prepared
Confidence
medium
Sources
4

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-285: 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-2023-3574 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.3 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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
6.3CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.3Medium
CVSS 3.0 vector shape for CVE-2023-3574Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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-frameworkunspecifiedListed
Weakness

CWE details

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

CWE-285 · source CWE mapping

Improper Authorization

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