# CVE-2025-12305: quequnlong shiyi-blog Job SysJobController.java deserialization

> Remote attackers can exploit a deserialization flaw in the Job Handler to execute arbitrary code, requiring authentication.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 27 Oct 2025
- **Also known as:** GHSA-rr87-h7hq-m7h7

## What is CVE-2025-12305?

CVE-2025-12305 is a medium-severity unsafe deserialization vulnerability in quequnlong shiyi-blog, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in quequnlong shiyi-blog up to 1.2.1. This impacts an unknown function of the file src/main/java/com/mojian/controller/SysJobController.java of the component Job Handler. The manipulation results in deserialization. The attack can be executed remotely. The exploit has been made public and could be used.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Quequnlong Shiyi-Blog.

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

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

## Is CVE-2025-12305 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12305 exists.

## Other vulnerabilities in quequnlong shiyi-blog

- [CVE-2025-5511](https://insights.sbomify.com/CVE-2025-5511/): quequnlong shiyi-blog photos improper authorization (medium 6.9)
- [CVE-2025-5512](https://insights.sbomify.com/CVE-2025-5512/): quequnlong shiyi-blog Administrator Backend verifyPassword improper authentication (medium 6.9)
- [CVE-2025-5509](https://insights.sbomify.com/CVE-2025-5509/): quequnlong shiyi-blog upload path traversal (medium 5.3)
- [CVE-2025-5510](https://insights.sbomify.com/CVE-2025-5510/): quequnlong shiyi-blog optimize server-side request forgery (medium 5.3)
- [CVE-2025-5513](https://insights.sbomify.com/CVE-2025-5513/): quequnlong shiyi-blog add cross site scripting (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12305 is a medium-severity unsafe deserialization vulnerability in quequnlong shiyi-blog, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12305 exists.

Affected product: quequnlong shiyi-blog. 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-12305/ (Markdown: https://insights.sbomify.com/CVE-2025-12305/index.md)
```

## Sources

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

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