# CVE-2024-49223: WordPress CJ Change Howdy plugin <= 3.3.1 - CSRF to Stored XSS vulnerability

> Attackers can trick users into performing actions that lead to stored XSS, potentially compromising WordPress sites using the CJ Change Howdy plugin.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Oct 2024
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-5g64-w7g9-m6pp

## What is CVE-2024-49223?

CVE-2024-49223 is a high-severity vulnerability in shibulijack CJ Change Howdy, published on 17 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in shibulijack CJ Change Howdy cj-change-howdy allows Cross Site Request Forgery.This issue affects CJ Change Howdy: from n/a through <= 3.3.1.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Shibulijack Cj Change Howdy.

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

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

## Is CVE-2024-49223 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-49223 is a high-severity vulnerability in shibulijack CJ Change Howdy, published on 17 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-49223 in the wild and no public exploit code.

Affected product: shibulijack CJ Change Howdy. 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-49223/ (Markdown: https://insights.sbomify.com/CVE-2024-49223/index.md)
```

## Sources

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

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