CVE-2026-25616: Blesta 3.x through 5.x before 5.13.3 mishandles input validation, aka CORE-5665.

Q: How do I fix CVE-2026-25616?

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

Q: Is CVE-2026-25616 being exploited?

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

Q: What does CVE-2026-25616 affect?

CVE-2026-25616 affects blesta. Severity is medium (CVSS 4.7). Blesta 3.x through 5.x before 5.13.3 mishandles input validation, aka CORE-5665.

Q: How urgent is CVE-2026-25616?

Priority 26/100. No elevated risk signals yet.

Routine

MEDIUM 4.7UPGRADE

CVE-2026-25616 is a medium-severity flaw (CVSS 4.7) 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 mishandles input validation, aka CORE-5665.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.7 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-79
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.2.0 and < 5.13.2

Fixed in: 5.13.2

Safe to downgrade to: a release before 3.2.0

1. Check installed version

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

2. UPGRADE to 5.13.2 (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.2.0 (Debian / Ubuntu)

apt-cache madison blesta sudo apt install blesta=<VERSION_BEFORE_3.2.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.2.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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: Blesta <= 5.13.1 - Cross-Site Scripting

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-25616?

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

Is CVE-2026-25616 being exploited?

CVE-2026-25616 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-25616 affect?

CVE-2026-25616 affects blesta. Severity is medium (CVSS 4.7). Blesta 3.x through 5.x before 5.13.3 mishandles input validation, aka CORE-5665.

How urgent is CVE-2026-25616?

Priority 26/100. No elevated risk signals yet.

Related CVEs

CVE-2026-25615 HIGH 7.2 UPGRADE Blesta 3.x through 5.x before 5.13.3 allows object injection, aka CORE-5668.
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