# CVE-2025-1520: PostHog ClickHouse Table Functions SQL Injection Remote Code Execution Vulnerability

> Authenticated attackers can execute arbitrary code via SQL injection in PostHog's ClickHouse table functions.

- **Severity:** High 7.1 (`CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2025
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-v64v-fq96-c5wv

## What is CVE-2025-1520?

CVE-2025-1520 is a high-severity SQL injection vulnerability in PostHog, published on 23 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PostHog ClickHouse Table Functions SQL Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of PostHog. Authentication is required to exploit this vulnerability.

The specific flaw exists within the implementation of the SQL parser. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of the database account. Was ZDI-CAN-25350.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-1520?

2 open source packages ship an affected version, including @posthog/plugin-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@posthog/plugin-server` | npm | All versions to 1.10.7 | None |
| `@posthog/plugin-server` | npm | All versions to 1.10.7 | None |

Products: Posthog Posthog.

## How do I fix CVE-2025-1520?

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

## Is CVE-2025-1520 being exploited?

There is no known exploitation of CVE-2025-1520 in the wild and no public exploit code.

## Other vulnerabilities in PostHog

- [CVE-2025-1521](https://insights.sbomify.com/CVE-2025-1521/): PostHog slack_incoming_webhook Server-Side Request Forgery Information Disclosure Vulnerability (high 7.1)
- [CVE-2025-1522](https://insights.sbomify.com/CVE-2025-1522/): PostHog database_schema Server-Side Request Forgery Information Disclosure Vulnerability (high 7.1)
- [CVE-2024-9710](https://insights.sbomify.com/CVE-2024-9710/): PostHog database_schema Server-Side Request Forgery Information Disclosure Vulnerability (high 7.1)
- [CVE-2022-0645](https://insights.sbomify.com/CVE-2022-0645/): Open redirect vulnerability via endpoint authorize_and_redirect/?redirect= in posthog/posthog (medium 6.1)
- [CVE-2023-46746](https://insights.sbomify.com/CVE-2023-46746/): Authenticated PostHog users vulnerable to SSRF (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1520 and fix it if it is affected.

What it is: CVE-2025-1520 is a high-severity SQL injection vulnerability in PostHog, published on 23 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1520 in the wild and no public exploit code.

Affected packages and fixed versions:
- @posthog/plugin-server (npm): affected all versions up to 1.10.7; no fix listed
- @posthog/plugin-server (npm): affected all versions up to 1.10.7; no fix listed

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-2025-1520/ (Markdown: https://insights.sbomify.com/CVE-2025-1520/index.md)
```

## Sources

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

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