# CVE-2022-3464: puppyCMS settings.php cross site scripting

> Remote attackers can inject malicious scripts via the site_name argument in puppyCMS admin settings, potentially compromising user sessions.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Oct 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-3qf4-wfmh-xq4w

## What is CVE-2022-3464?

CVE-2022-3464 is a medium-severity cross-site scripting vulnerability in unspecified puppyCMS, published on 12 Oct 2022. 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

A vulnerability classified as problematic has been found in puppyCMS up to 5.1. This affects an unknown part of the file /admin/settings.php. The manipulation of the argument site_name leads to cross site scripting. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-210699.

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

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

It affects 1 product.


Products: Puppycms Puppycms.

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

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

## Is CVE-2022-3464 being exploited?

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

Public exploit code:

- A vulnerability classified as problematic has been found in puppyCMS up to 5.1. This affects an unknown part of the file /admin/settings.php. The manipulation of the argument site_name leads to cross site scripting. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-2 CVE project by @Sn0wAlice (github_poc): https://github.com/GYLQ/CVE-2022-3464

## Other vulnerabilities in unspecified puppyCMS

- [CVE-2020-18890](https://insights.sbomify.com/CVE-2020-18890/): Missing authorization in n/a (critical 9.8)
- [CVE-2020-18888](https://insights.sbomify.com/CVE-2020-18888/): Missing authorization in n/a (high 7.5)
- [CVE-2020-18889](https://insights.sbomify.com/CVE-2020-18889/): Cross-site request forgery in n/a (medium 6.5)
- [CVE-2018-15847](https://insights.sbomify.com/CVE-2018-15847/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3464 is a medium-severity cross-site scripting vulnerability in unspecified puppyCMS, published on 12 Oct 2022. 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-2022-3464 in the wild and no public exploit code.

Affected product: unspecified puppyCMS. 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-3464/ (Markdown: https://insights.sbomify.com/CVE-2022-3464/index.md)
```

## Sources

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

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