# CVE-2005-1452: Missing authorization in n/a

> Chief users can hide plugins installed by other users, bypassing intended visibility controls in Serendipity.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 3 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c6pw-7wcm-h3xx

## What is CVE-2005-1452?

CVE-2005-1452 is a critical missing authorization vulnerability in S9y Serendipity, published on 3 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Serendipity before 0.8 allows Chief users to "hide plugins installed by other users."

## Which versions are affected by CVE-2005-1452?

It affects 1 product.


Products: S9y Serendipity.

## How do I fix CVE-2005-1452?

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

## Is CVE-2005-1452 being exploited?

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

## Other vulnerabilities in S9y Serendipity

- [CVE-2005-1449](https://insights.sbomify.com/CVE-2005-1449/): Other in n/a (critical 10.0)
- [CVE-2020-10964](https://insights.sbomify.com/CVE-2020-10964/): File upload in n/a (critical 9.8)
- [CVE-2011-1134](https://insights.sbomify.com/CVE-2011-1134/): Cross-site scripting in n/a (critical 9.8)
- [CVE-2016-10752](https://insights.sbomify.com/CVE-2016-10752/): File upload in n/a (critical 9.8)
- [CVE-2016-10082](https://insights.sbomify.com/CVE-2016-10082/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1452 and fix it if it is affected.

What it is: CVE-2005-1452 is a critical missing authorization vulnerability in S9y Serendipity, published on 3 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-1452 in the wild and no public exploit code.

Affected product: S9y Serendipity. 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-2005-1452/ (Markdown: https://insights.sbomify.com/CVE-2005-1452/index.md)
```

## Sources

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

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