# CVE-2025-13576: code-projects Blog Site admin.php improper authorization

> Remote attackers can bypass authorization checks in the admin panel to perform unauthorized actions, requiring immediate attention from site administrators.

- **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:** 24 Nov 2025
- **Updated:** 24 Nov 2025
- **Also known as:** GHSA-q2cr-96j4-c73w

## What is CVE-2025-13576?

CVE-2025-13576 is a medium-severity missing authorization vulnerability in code-projects Blog Site, published on 24 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in code-projects Blog Site 1.0. The affected element is an unknown function of the file /admin.php. Performing manipulation results in improper authorization. It is possible to initiate the attack remotely. The exploit is now public and may be used. Multiple endpoints are affected.

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

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

It affects 1 product.


Products: Fabian Blog Site.

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

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

## Is CVE-2025-13576 being exploited?

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

## Other vulnerabilities in code-projects Blog Site

- [CVE-2025-13575](https://insights.sbomify.com/CVE-2025-13575/): code-projects Blog Site Category blog.php category_exists sql injection (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13576 is a medium-severity missing authorization vulnerability in code-projects Blog Site, published on 24 Nov 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-13576 exists.

Affected product: code-projects Blog Site. 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-13576/ (Markdown: https://insights.sbomify.com/CVE-2025-13576/index.md)
```

## Sources

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

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