# CVE-2022-50945: WordPress 3dady Real-Time Web Stats 1.0 Stored XSS

> Authenticated attackers can inject malicious JavaScript via unsanitized input fields in the 3dady Real-Time Web Stats plugin, leading to arbitrary code execution.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA: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:** 10 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-pcph-8p5m-wmw7

## What is CVE-2022-50945?

CVE-2022-50945 is a medium-severity cross-site scripting vulnerability in 3dady real-time web stats, published on 10 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

WordPress 3dady Real-Time Web Stats plugin 1.0 contains a stored cross-site scripting vulnerability that allows authenticated attackers to inject malicious JavaScript by exploiting unsanitized input fields. Attackers can insert JavaScript payloads in the dady_input_text or dady2_input_text fields via the plugin options panel to execute arbitrary code when the page is viewed.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2022-50945 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50945 is a medium-severity cross-site scripting vulnerability in 3dady real-time web stats, published on 10 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50945 exists.

Affected product: 3dady real-time web 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-50945/ (Markdown: https://insights.sbomify.com/CVE-2022-50945/index.md)
```

## Sources

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

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