# CVE-2025-5511: quequnlong shiyi-blog photos improper authorization

> Remote attackers can access or modify album photos without proper authorization due to missing checks in the shiyi-blog application.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2025
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-mjq6-f642-426f

## What is CVE-2025-5511?

CVE-2025-5511 is a medium-severity missing authorization vulnerability in quequnlong shiyi-blog, published on 3 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in quequnlong shiyi-blog up to 1.2.1. This issue affects some unknown processing of the file /dev api/app/album/photos/. The manipulation leads to improper authorization. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Quequnlong Shiyi-Blog.

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

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

## Is CVE-2025-5511 being exploited?

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

## Other vulnerabilities in quequnlong shiyi-blog

- [CVE-2025-5512](https://insights.sbomify.com/CVE-2025-5512/): quequnlong shiyi-blog Administrator Backend verifyPassword improper authentication (medium 6.9)
- [CVE-2025-12305](https://insights.sbomify.com/CVE-2025-12305/): quequnlong shiyi-blog Job SysJobController.java deserialization (medium 5.3)
- [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-5511 and fix it if it is affected.

What it is: CVE-2025-5511 is a medium-severity missing authorization vulnerability in quequnlong shiyi-blog, published on 3 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5511 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-5511/ (Markdown: https://insights.sbomify.com/CVE-2025-5511/index.md)
```

## Sources

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

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