# CVE-2022-44738: WordPress Posts and Users Stats Plugin <= 1.1.3 is vulnerable to CSV Injection

> Attackers can inject malicious formulas into CSV exports, potentially executing code when the file is opened in spreadsheet software.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Nov 2023
- **Updated:** 28 Apr 2026

## What is CVE-2022-44738?

CVE-2022-44738 is a medium-severity code injection vulnerability in Patrick Robrecht Posts and Users Stats, published on 7 Nov 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Formula Elements in a CSV File vulnerability in Patrick Robrecht Posts and Users Stats.This issue affects Posts and Users Stats: from n/a through 1.1.3.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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

It affects 1 product.


Products: Patrickrobrecht Posts and Users Stats.

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

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

## Is CVE-2022-44738 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44738 is a medium-severity code injection vulnerability in Patrick Robrecht Posts and Users Stats, published on 7 Nov 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-44738 in the wild and no public exploit code.

Affected product: Patrick Robrecht Posts and Users Stats. 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-44738/ (Markdown: https://insights.sbomify.com/CVE-2022-44738/index.md)
```

## Sources

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

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