# CVE-2022-4550: User Activity <= 1.0.1 - IP Spoofing

> Attackers can spoof IP addresses in User Activity logs by manipulating X-Forwarded-For headers, compromising audit integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 27 Feb 2023
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-62gq-fgj3-92v6

## What is CVE-2022-4550?

CVE-2022-4550 is a high-severity vulnerability in Unknown User Activity, published on 27 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The User Activity WordPress plugin through 1.0.1 checks headers such as the X-Forwarded-For to retrieve the IP address of the request, which could lead to IP spoofing

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: User Activity Project User Activity.

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

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

## Is CVE-2022-4550 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4550 is a high-severity vulnerability in Unknown User Activity, published on 27 Feb 2023. 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-4550 exists.

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

## Sources

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

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