# CVE-2022-2834: Helpful < 4.5.26 - Information Disclosure

> Attackers can download publicly accessible log files to retrieve sensitive user data like IPs and emails from the Helpful plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2022
- **Updated:** 13 May 2025
- **Also known as:** GHSA-6j5r-8vhm-p3x4

## What is CVE-2022-2834?

CVE-2022-2834 is a medium-severity vulnerability in Unknown Helpful, published on 17 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Helpful WordPress plugin before 4.5.26 puts the exported logs and feedbacks in a publicly accessible location and guessable names, which could allow attackers to download them and retrieve sensitive information such as IP, Names and Email Address depending on the plugin's settings

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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

It affects 1 product.


Products: Helpful Project Helpful.

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

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

## Is CVE-2022-2834 being exploited?

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

## Other vulnerabilities in Unknown Helpful

- [CVE-2021-24841](https://insights.sbomify.com/CVE-2021-24841/): Helpful < 4.4.59 - Admin+ Stored Cross-Site Scripting (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2834 is a medium-severity vulnerability in Unknown Helpful, published on 17 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2834 exists.

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

## Sources

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

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