# Wallabag user can reset data unintentionally

Advisory record · `GHSA-p8gp-899c-jvq9`

- **Identifiers:** `GHSA-p8gp-899c-jvq9` · `CVE-2023-4454` · `PKSA-grtz-7vrv-bfdf`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 21 Aug 2023
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Aug 2023, 20:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wallabag/wallabag` (Packagist): affected `>=2.0.0-alpha.1, <2.6.3`; fixed in `2.6.3`

## Machine-written summary

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

> Wallabag versions from 2.0.0-alpha.1 before 2.6.3 are vulnerable to cross-site request forgery, which lets an attacker reset a user's annotations, entries, tags, or archived entries. An attacker would need to get a logged-in user to visit a malicious third-party website. Upgrade to wallabag 2.6.3 or later, where these actions require a POST request.

Written 4 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

- 4.3 Medium, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`, from CNA (@huntrdev)

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

## Timeline

- 31 Oct 2026, 14:31 UTC: First seen by agentprime
- 31 Oct 2026, 14:31 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-p8gp-899c-jvq9)

## Sources

- [GitHub Advisory Database: GHSA-p8gp-899c-jvq9](https://github.com/advisories/GHSA-p8gp-899c-jvq9)
- [OSV: GHSA-p8gp-899c-jvq9](https://osv.dev/vulnerability/GHSA-p8gp-899c-jvq9)
- <https://github.com/wallabag/wallabag/security/advisories/GHSA-p8gp-899c-jvq9>
- <https://github.com/wallabag/wallabag/commit/78b0b55c40511e1f22d5bbb4897aa10fca68441c>
- <https://github.com/wallabag/wallabag>
- <https://huntr.dev/bounties/4ee0ef74-e4d4-46e7-a05c-076bce522299>

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-p8gp-899c-jvq9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p8gp-899c-jvq9/>. Everything for agents: <https://agentprime.io/llms.txt>.
