# Flarum Vulnerable to Session Hijacking via Authoritative Subdomain Cookie Overwrite

Advisory record · `GHSA-hg9j-64wp-m9px`

- **Identifiers:** `GHSA-hg9j-64wp-m9px` · `CVE-2025-27794` · `PKSA-p7h1-3152-gpfx` · `PKSA-wm5r-h6h3-m2pf`
- **State:** Confirmed
- **Severity:** CVSS 6.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-74](https://cwe.mitre.org/data/definitions/74.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md)
- **Published:** 12 Mar 2025
- **Updated:** 12 Mar 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 12 Mar 2025, 22:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `flarum/core` (Packagist): affected `<1.8.10`; fixed in `1.8.10`
- `flarum/framework` (Packagist): affected `<1.8.10`; fixed in `1.8.10`

## Machine-written summary

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

> Flarum packages flarum/core and flarum/framework, versions before 1.8.10, are affected. An attacker who controls a subdomain under the same parent domain as a Flarum forum could set cookies scoped to the parent domain and replace a victim's session token, potentially taking over the victim's session. The source gives few details and says the attack does not seem exploitable in practice because of browser protections. Upgrade flarum/core and flarum/framework to 1.8.10 or later. No other workaround is listed.

Written 3 Nov 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

- 6.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:27 UTC: First seen by agentprime
- 31 Oct 2026, 14:27 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hg9j-64wp-m9px)

## Sources

- [GitHub Advisory Database: GHSA-hg9j-64wp-m9px](https://github.com/advisories/GHSA-hg9j-64wp-m9px)
- [OSV: GHSA-hg9j-64wp-m9px](https://osv.dev/vulnerability/GHSA-hg9j-64wp-m9px)
- <https://github.com/flarum/framework/security/advisories/GHSA-hg9j-64wp-m9px>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-27794>
- <https://github.com/flarum/framework/commit/a05aaea3ee1e0a8b870935183193cd6052f1d402>
- <https://github.com/flarum/framework>
- <https://github.com/flarum/framework/releases/tag/v1.8.10>

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-hg9j-64wp-m9px>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hg9j-64wp-m9px/>. Everything for agents: <https://agentprime.io/llms.txt>.
