LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25240: An improper SameSite Attribute vulnerability in pimCore v10.5.15 allows attackers to execute arbitrary code.

An improper SameSite Attribute vulnerability in pimCore v10.5.15 allows attackers to execute arbitrary code.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-25240 is reported in pimCore v10.5.15 and involves improper SameSite cookie handling. The record says it may allow arbitrary code execution, but the public details are sparse. Treat exposed administrative or authenticated Pimcore deployments as higher concern until vendor guidance confirms impact and fixes.

Executive priority

High priority for teams running Pimcore 10.5.15, especially if administration is internet-accessible. The severity is high, but urgency should be balanced by the lack of confirmed active exploitation in the provided sources.

Technical view

The CVE maps to CWE-1265 and CVSS 8.8 with network access, low complexity, no privileges, and required user interaction. The available sources point to SameSite bypass concepts and a public third-party repository, but do not fully document the chain from cookie attribute weakness to code execution.

Likely exposure

Organizations running pimCore v10.5.15 are the only clearly named exposure. The structured affected-product metadata is incomplete, so do not assume other Pimcore versions are affected without vendor confirmation.

Exploitation context

No CISA KEV listing is provided, and the bundle does not cite active exploitation. Public technical material appears to exist, but the evidence supplied is insufficient to claim exploitation in the wild.

Researcher notes

The record is thin and internally under-explained: SameSite misconfiguration is identified, while arbitrary code execution impact is asserted without a complete public chain in the supplied bundle. Validate against primary vendor advisories before broad scoping.

Mitigation direction

  • Check Pimcore vendor guidance for affected versions and fixed releases.
  • Prioritize review of any pimCore v10.5.15 deployments.
  • Restrict administrative access to trusted networks where feasible.
  • Review cookie SameSite, Secure, and HttpOnly settings against vendor guidance.
  • Monitor logs for suspicious authenticated admin actions.

Validation and detection

  • Inventory Pimcore instances and confirm exact versions.
  • Identify internet-facing Pimcore administrative interfaces.
  • Review application cookies for SameSite configuration issues.
  • Check whether compensating controls limit cross-site request exposure.
  • Verify remediation only against vendor-published guidance.
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-1265: 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-2023-25240 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-25240Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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
n/an/an/aListed
Weakness

CWE details

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

CWE-1265 · source CWE mapping

Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls

Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.