# CVE-2022-48435: Information disclosure in PhpStorm

> Attackers with local access can read sensitive source code from log files in JetBrains PhpStorm.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 4 Apr 2023
- **Updated:** 11 Feb 2025
- **Also known as:** GHSA-5v5x-x8hh-7ffj

## What is CVE-2022-48435?

CVE-2022-48435 is a low-severity vulnerability in JetBrains PhpStorm, published on 4 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In JetBrains PhpStorm before 2023.1 source code could be logged in the local idea.log file

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2022-48435?

It affects 1 product.


Products: Jetbrains Phpstorm.

## How do I fix CVE-2022-48435?

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

## Is CVE-2022-48435 being exploited?

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

## Other vulnerabilities in JetBrains PhpStorm

- [CVE-2026-64808](https://insights.sbomify.com/CVE-2026-64808/): Code injection in PhpStorm (high 8.4)
- [CVE-2026-64809](https://insights.sbomify.com/CVE-2026-64809/): Code injection in PhpStorm (high 8.4)
- [CVE-2021-25764](https://insights.sbomify.com/CVE-2021-25764/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48435 and fix it if it is affected.

What it is: CVE-2022-48435 is a low-severity vulnerability in JetBrains PhpStorm, published on 4 Apr 2023. 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-2022-48435 in the wild and no public exploit code.

Affected product: JetBrains PhpStorm. 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-2022-48435/ (Markdown: https://insights.sbomify.com/CVE-2022-48435/index.md)
```

## Sources

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

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