# BaserCMS privilege escallation

Advisory record · `GHSA-6wr6-54mw-mvhr`

- **Identifiers:** `GHSA-6wr6-54mw-mvhr` · `CVE-2011-2674` · `PKSA-vqx1-gmmm-2jdv`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-269](https://cwe.mitre.org/data/definitions/269.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md)
- **Published:** 13 May 2022
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 May 2022, 01:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `baserproject/basercms` (Packagist): affected `<1.6.12`; fixed in `1.6.12`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> BaserCMS versions before 1.6.12 (Packagist package baserproject/basercms) do not properly restrict who can be added to the operators group. Per the source, a remote authenticated user can gain privileges through unspecified vectors. Upgrade to baserproject/basercms 1.6.12 or later, which contains the fix.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.013, the 71st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:04 UTC: First seen by agentprime
- 31 Oct 2026, 14:04 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6wr6-54mw-mvhr)

## Sources

- [GitHub Advisory Database: GHSA-6wr6-54mw-mvhr](https://github.com/advisories/GHSA-6wr6-54mw-mvhr)
- [OSV: GHSA-6wr6-54mw-mvhr](https://osv.dev/vulnerability/GHSA-6wr6-54mw-mvhr)
- <https://nvd.nist.gov/vuln/detail/CVE-2011-2674>
- <https://github.com/baserproject/basercms>
- <http://basercms.net/patch/JVN09789751>
- <http://jvn.jp/en/jp/JVN16617002/index.html>
- <http://jvndb.jvn.jp/jvndb/JVNDB-2011-000066>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6wr6-54mw-mvhr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6wr6-54mw-mvhr/>. Everything for agents: <https://agentprime.io/llms.txt>.
