# CVE-2023-4281: Activity Log < 2.8.8 - IP Spoofing

> Attackers can spoof IP addresses in the Activity Log plugin by manipulating untrusted headers, hiding their identity and bypassing security controls.

- **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:** 25 Sep 2023
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-4g74-7gvh-m4wg

## What is CVE-2023-4281?

CVE-2023-4281 is a medium-severity vulnerability in Unknown Activity Log, published on 25 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This Activity Log WordPress plugin before 2.8.8 retrieves client IP addresses from potentially untrusted headers, allowing an attacker to manipulate its value. This may be used to hide the source of malicious traffic.

## Which versions are affected by CVE-2023-4281?

It affects 1 product.


Products: Activity Log Project Activity Log.

## How do I fix CVE-2023-4281?

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

## Is CVE-2023-4281 being exploited?

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

Public exploit code:

- Repository for CVE-2023-4281 vulnerability.  (github_poc): https://github.com/b0marek/CVE-2023-4281

## Other vulnerabilities in Unknown Activity Log

- [CVE-2022-27858](https://insights.sbomify.com/CVE-2022-27858/): WordPress Activity Log plugin <= 2.8.3 - CSV Injection vulnerability (high 7.4)
- [CVE-2022-3941](https://insights.sbomify.com/CVE-2022-3941/): Activity Log Plugin HTTP Header neutralization for logs (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4281 and fix it if it is affected.

What it is: CVE-2023-4281 is a medium-severity vulnerability in Unknown Activity Log, published on 25 Sep 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-2023-4281 exists.

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

## Sources

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

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