Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-31103: Untrusted data deserialization vulnerability exists in a-blog cms

42
This month
HIGH 7.5REMOTEUPGRADE

CVE-2025-31103 is a high-severity flaw (CVSS 7.5) affecting a-blog cms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Untrusted data deserialization vulnerability exists in a-blog cms. Processing a specially crafted request may store arbitrary files on the server where the product is running. This can be leveraged to execute an arbitrary script on the server.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.5% (top 58%)
CISA exploited listNo
WeaknessCWE-502
Published2025-03-31
Last modified2026-06-17
Publisher (CNA): JPCERT/CC · Vendor: appleple

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

appleple a-blog cms UPGRADE
Affected: <= 2.8.80 · >= 2.9.0 and <= 2.9.46 · >= 2.10.0 and < 2.10.58 · >= 2.11.0 and < 2.11.70 · >= 3.0.0 and < 3.0.41 · >= 3.1.0 and < 3.1.37
Fixed in: 2.10.58, 2.11.70, 3.0.41, 3.1.37
Safe to downgrade to: a release before 2.9.0
1. Check installed version
apt-cache policy a-blog-cms || rpm -q a-blog-cms || a-blog-cms --version
2. UPGRADE to 2.10.58 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade a-blog-cms
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade a-blog-cms
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 2.9.0 (Debian / Ubuntu)
apt-cache madison a-blog-cms sudo apt install a-blog-cms=<VERSION_BEFORE_2.9.0> sudo apt-mark hold a-blog-cms
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list a-blog-cms sudo dnf downgrade a-blog-cms-<VERSION_BEFORE_2.9.0> sudo dnf versionlock add a-blog-cms
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-2025-31103?

a-blog cms: upgrade to 2.10.58, 2.11.70, 3.0.41, 3.1.37. Exact commands for each OS are on this page.

Is CVE-2025-31103 being exploited?

CVE-2025-31103 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-2025-31103 affect?

CVE-2025-31103 affects a-blog cms. Severity is high (CVSS 7.5). Untrusted data deserialization vulnerability exists in a-blog cms. Processing a specially crafted request may store arbitrary files on the server where the product is running. This can be leveraged to execute an arbitrary script on the serv

How urgent is CVE-2025-31103?

Priority 42/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.