LiveActive security incident?Get immediate response
CVE Record

CVE-2025-56422: A deserialization vulnerability in LimeSurvey before v6.15.0+250623 allows a remote attacker to execute arb...

A deserialization vulnerability in LimeSurvey before v6.15.0+250623 allows a remote attacker to execute arbitrary code on the server.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-56422 is a critical LimeSurvey flaw reported in versions before v6.15.0+250623. It can let a remote unauthenticated attacker run code on the server, potentially compromising survey data and the hosting system.

Executive priority

Handle as urgent for any exposed LimeSurvey deployment. The combination of critical CVSS, unauthenticated network reachability, and possible server code execution creates material business risk.

Technical view

The vulnerability is CWE-502 unsafe deserialization in LimeSurvey before v6.15.0+250623. The CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction required.

Likely exposure

Organizations running internet-accessible LimeSurvey versions earlier than v6.15.0+250623 should treat exposure as high. The source bundle does not provide CPEs or detailed affected-version ranges beyond that cutoff.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. The risk remains severe because the described impact is remote arbitrary code execution without authentication.

Researcher notes

Public details in the bundle are sparse. The record identifies LimeSurvey, unsafe deserialization, and the version cutoff, but does not provide affected CPEs, attack surface specifics, indicators, or confirmed exploitation.

Mitigation direction

  • Upgrade LimeSurvey to v6.15.0+250623 or later where applicable.
  • Check LimeSurvey vendor guidance for any additional remediation instructions.
  • Reduce internet exposure for affected LimeSurvey instances until remediated.
  • Prioritize backup review and recovery readiness for impacted servers.

Validation and detection

  • Inventory all LimeSurvey deployments and confirm their exact versions.
  • Flag any instance running earlier than v6.15.0+250623.
  • Confirm whether affected instances are reachable from the internet.
  • Review application and server logs for unusual errors or unexpected code execution indicators.
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 · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-2025-56422 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-56422Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
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-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.