# CVE-2025-31103: Deserialization in a-blog cms (Ver. 2.8.x series)

> An attacker can exploit untrusted data deserialization in a-blog cms to store arbitrary files and execute scripts on the server.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** GHSA-hhgp-h65v-gf93

## What is CVE-2025-31103?

CVE-2025-31103 is a high-severity unsafe deserialization vulnerability in appleple inc. a-blog cms (Ver. 2.8.x series), published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-31103?

It affects 1 product.


Products: Appleple A-Blog Cms.

## How do I fix CVE-2025-31103?

No fix has been published for CVE-2025-31103 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-31103 being exploited?

There is no known exploitation of CVE-2025-31103 in the wild and no public exploit code.

## Other vulnerabilities in appleple inc. a-blog cms (Ver. 2.8.x series)

- [CVE-2022-21142](https://insights.sbomify.com/CVE-2022-21142/): Auth bypass in a-blog cms (critical 9.8)
- [CVE-2025-36560](https://insights.sbomify.com/CVE-2025-36560/): Server-side request forgery in a-blog cms (critical 9.2)
- [CVE-2024-23180](https://insights.sbomify.com/CVE-2024-23180/): File upload in a-blog cms (high 8.8)
- [CVE-2024-23348](https://insights.sbomify.com/CVE-2024-23348/): Cross-site scripting in a-blog cms (high 8.8)
- [CVE-2024-23182](https://insights.sbomify.com/CVE-2024-23182/): Path traversal in a-blog cms (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31103 and fix it if it is affected.

What it is: CVE-2025-31103 is a high-severity unsafe deserialization vulnerability in appleple inc. a-blog cms (Ver. 2.8.x series), published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31103 in the wild and no public exploit code.

Affected product: appleple inc. a-blog cms (Ver. 2.8.x series). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-31103/ (Markdown: https://insights.sbomify.com/CVE-2025-31103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-31103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-31103
- OSV: https://osv.dev/vulnerability/CVE-2025-31103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-31103/
Summaries are generated and may contain mistakes; the official description above is the record.