# CVE-2024-0970: User Activity Tracking and Log < 4.1.4 - IP Spoofing

> Attackers can spoof IP addresses in logs by manipulating untrusted headers, compromising the integrity of user activity tracking records.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 15 May 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-v8j5-hjg7-w5w5

## What is CVE-2024-0970?

CVE-2024-0970 is a medium-severity vulnerability in Unknown User Activity Tracking and Log, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This User Activity Tracking and Log WordPress plugin before 4.1.4 retrieves client IP addresses from potentially untrusted headers, allowing an attacker to manipulate its value.

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

It affects 1 product.


Products: Mooveagency User Activity Tracking and Log.

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

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

## Is CVE-2024-0970 being exploited?

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

## Other vulnerabilities in Unknown User Activity Tracking and Log

- [CVE-2023-4150](https://insights.sbomify.com/CVE-2023-4150/): User Activity Tracking and Log < 4.0.9 - License Update/Deactivation via CSRF (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0970 is a medium-severity vulnerability in Unknown User Activity Tracking and Log, published on 15 May 2025. 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-2024-0970 exists.

Affected product: Unknown User Activity Tracking and Log. 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-0970/ (Markdown: https://insights.sbomify.com/CVE-2024-0970/index.md)
```

## Sources

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

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