CVE-2025-56422
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA deserialization vulnerability in LimeSurvey before v6.15.0+250623 allows a remote attacker to execute arbitrary code on the server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA deserialization flaw in LimeSurvey versions prior to v6.15.0+250623 allows unauthenticated remote attackers to deserialize untrusted data in a way that leads to arbitrary code execution on the underlying server. This is a critical deserialization vulnerability commonly exploited via crafted PHP object injection payloads.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 6.14.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check LimeSurvey version in admin panelLog into the LimeSurvey admin interface and navigate to the home/dashboard page, or check the version by examining the application source files (version.php or similar).Affected if The installed version is 6.14.3 or any version prior to v6.15.0+250623
-
Check version from command line or filesIf you have filesystem access, locate the version file in the LimeSurvey installation directory (commonly in application/config/version.php or similar), or check the git commit hash if deployed from source.Affected if The version file shows a build/commit prior to 250623 or a version below 6.15.0
-
Verify application is network accessibleConfirm the LimeSurvey web application is reachable over HTTP/HTTPS. Since this vulnerability can be exploited without authentication, check if the application is exposed to network access.Affected if The LimeSurvey instance is accessible over the network and runs a vulnerable version listed above
If LimeSurvey version is 6.14.3 or lower (any version prior to v6.15.0+250623) and the application is network-accessible, the environment is vulnerable to CVE-2025-56422.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade LimeSurvey to version v6.15.0+250623 or later. If immediate patching is not possible, restrict network access to the application and disable PHP object serialization features at the web server level.
LimeSurvey v6.15.0+250623 or later stable release
- 1. Identify the current LimeSurvey version by checking the application or configuration files
- 2. Create a complete backup of the LimeSurvey database and all application files
- 3. Download LimeSurvey v6.15.0+250623 or a later stable version from the official GitHub repository (github.com/LimeSurvey/LimeSurvey)
- 4. Extract the new version files to the web server document root, replacing the existing installation
- 5. Run any database migration scripts if included in the upgrade package
- 6. Clear any cached files (temp, runtime directories) to ensure fresh application state
- 7. Verify the installation by accessing the LimeSurvey admin interface and confirming the version number
- 8. Test critical functionality to ensure the upgrade did not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56422 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-56422 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data