dbcve.org
BlestaApplication · Phillipsdata

CVE-2026-25614

HIGH · 7.5 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 5.13.2 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Blesta 3.x through 5.x before 5.13.3 allows object injection, aka CORE-5680.

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 · moderate confidence

Blesta versions 3.x through 5.x before 5.13.3 contains an object injection vulnerability (CWE-502). The application deserializes untrusted input without proper validation, potentially allowing remote attackers to instantiate arbitrary PHP objects and execute arbitrary code via crafted serialized data.

MitigationUpdate Blesta to version 5.13.3 or later to obtain the vendor patch. If immediate patching is not possible, review and restrict any user-supplied data being passed to PHP unserialize() functions.

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
BlestaApplication
Affected:>= 3.0.0, < 5.13.2

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Work through these to decide whether this CVE applies to you.

  1. Identify Blesta installation
    Locate the Blesta installation directory and look for a version file or check the composer.json / config/version.php for the installed version number
    Affected if The installed version is 3.0.0 through 5.13.2 (versions before 5.13.3)
  2. Confirm the exact version number
    Run: cat /path/to/blesta/config/version.php or check composer.lock for the blesta package version
    Affected if Version shown is less than 5.13.3
  3. Identify PHP files using unserialize on user input
    Search the Blesta source code for patterns like unserialize($_POST, unserialize($_GET, unserialize($_REQUEST, or similar calls where user-supplied data is passed directly to unserialize()
    Affected if Any PHP files in the Blesta installation unserialize data derived from user input without sanitization
  4. Check for deserialization entry points
    Review PHP application logs and HTTP access logs for requests containing serialized PHP objects in POST/GET parameters that get processed by Blesta
    Affected if Application processes serialized data from untrusted sources without validation
  5. Verify PHP unserialize usage in Blesta core
    Grep the Blesta source for 'unserialize' calls and examine whether they handle data from client requests: grep -r "unserialize" /path/to/blesta/ --include="*.php"
    Affected if unserialize() calls exist that process user-supplied data without prior validation or use of allowed_classes parameter

A user is affected if their Blesta installation version is 3.0.0 through 5.13.2 and the application deserializes untrusted user input via PHP's unserialize() function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.13.2 or later
Fixed in 5.13.2
Interim mitigation

Update Blesta to version 5.13.3 or later to obtain the vendor patch. If immediate patching is not possible, review and restrict any user-supplied data being passed to PHP unserialize() functions.

Recommended fix Moderate confidence

5.13.3

  1. Backup the Blesta database and all files before proceeding
  2. Download Blesta version 5.13.3 or the latest stable release from the official Blesta website (www.blesta.com)
  3. Extract the upgrade package to a temporary location
  4. Place the site in maintenance mode or ensure no users are accessing it during upgrade
  5. Upload the new files, overwriting the existing installation (or follow Blesta's specific upgrade documentation for your installation method)
  6. Run any database migration scripts if included in the upgrade package
  7. Clear any cached data (temporary files, opcode caches)
  8. Verify the installation by logging in and checking core functionality
Caveat Review Blesta 5.13.3 release notes for any breaking changes or required configuration updates before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Blesta Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25614 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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