CVE-2026-25615: Blesta 3.x through 5.x before 5.13.3 allows object injection, aka CORE-5668.

Routine

HIGH 7.2UPGRADE

CVE-2026-25615 is a high-severity flaw (CVSS 7.2) affecting blesta. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Blesta 3.x through 5.x before 5.13.3 allows object injection, aka CORE-5668.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-502
Published	2026-02-03
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: phillipsdata

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-03 20:15 UTCPublished CVE record published
2026-06-17 10:24 UTCUpdated Record last modified

phillipsdata blesta UPGRADE

Affected: >= 3.0.0 and < 5.13.3

Fixed in: 5.13.3

Safe to downgrade to: a release before 3.0.0

1. Check installed version

apt-cache policy blesta || rpm -q blesta || blesta --version

2. UPGRADE to 5.13.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade blesta

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade blesta

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)

apt-cache madison blesta sudo apt install blesta=<VERSION_BEFORE_3.0.0> sudo apt-mark hold blesta

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list blesta sudo dnf downgrade blesta-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add blesta

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-25615?

blesta: upgrade to 5.13.3. Exact commands for each OS are on this page.

Is CVE-2026-25615 being exploited?

CVE-2026-25615 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-25615 affect?

CVE-2026-25615 affects blesta. Severity is high (CVSS 7.2). Blesta 3.x through 5.x before 5.13.3 allows object injection, aka CORE-5668.

How urgent is CVE-2026-25615?

Priority 36/100. High severity

Related CVEs

CVE-2026-25616 MEDIUM 4.7 UPGRADE Blesta 3.x through 5.x before 5.13.3 mishandles input validation, aka CORE-5665.
CVE-2026-25614 HIGH 7.5 UPGRADE Blesta 3.x through 5.x before 5.13.3 allows object injection, aka CORE-5680.

References

← Back to latest CVEs