# CVE-2024-30252: GitHub Security Lab (GHSL) Vulnerability Report, livemarks: `GHSL-2024-015`

> A malicious website can force the Livemarks extension to send authenticated requests to arbitrary URLs, potentially compromising private network servers.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Apr 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-3gg9-w4fm-jjcg

## What is CVE-2024-30252?

CVE-2024-30252 is a low-severity vulnerability in nt1m livemarks, published on 4 Apr 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Livemarks is a browser extension that provides RSS feed bookmark folders. Versions of Livemarks prior to 3.7 are vulnerable to cross-site request forgery. A malicious website may be able to coerce the extension to send an authenticated GET request to an arbitrary URL. An authenticated request is a request where the cookies of the browser are sent along with the request. The `subscribe.js` script uses the first parameter from the current URL location as the URL of the RSS feed to subscribe to and checks that the RSS feed is valid XML. `subscribe.js` is accessible by an attacker website due to its use in `subscribe.html`, an HTML page that is declared as a `web_accessible_resource` in `manifest.json`. This issue may lead to `Privilege Escalation`. A CSRF breaks the integrity of servers running on a private network. A user of the browser extension may have a private server with dangerous functionality, which is assumed to be safe due to network segmentation. Upon receiving an authenticated request instantiated from an attacker, this integrity is broken. Version 3.7 fixes this issue by removing subscribe.html from `web_accessible_resources`.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-30252?


## How do I fix CVE-2024-30252?

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

## Is CVE-2024-30252 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30252 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30252 and fix it if it is affected.

What it is: CVE-2024-30252 is a low-severity vulnerability in nt1m livemarks, published on 4 Apr 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30252 exists.

Affected product: nt1m livemarks. 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-2024-30252/ (Markdown: https://insights.sbomify.com/CVE-2024-30252/index.md)
```

## Sources

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

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