CVE-2022-3464: A vulnerability classified as problematic has been found in puppyCMS up to 5.1

Q: How do I fix CVE-2022-3464?

puppycms: upgrade to newer than 5.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-3464 being exploited?

CVE-2022-3464 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-3464 affect?

CVE-2022-3464 affects puppycms. Severity is medium (CVSS 4.3). 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 initia

Q: How urgent is CVE-2022-3464?

Priority 28/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2022-3464 is a medium-severity flaw (CVSS 4.3) affecting puppycms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.7% (top 48%)
CISA exploited list	No
Weakness	CWE-707, CWE-79
Published	2022-10-12
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: puppycms

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-10-12 10:15 UTCPublished CVE record published
2026-06-17 04:59 UTCUpdated Record last modified

puppycms puppycms UPGRADE

Affected: <= 5.1

Fixed in: newer than 5.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy puppycms || rpm -q puppycms || puppycms --version

2. UPGRADE to newer than 5.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade puppycms

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade puppycms

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-3464?

puppycms: upgrade to newer than 5.1. Exact commands for each OS are on this page.

Is CVE-2022-3464 being exploited?

CVE-2022-3464 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-3464 affect?

CVE-2022-3464 affects puppycms. Severity is medium (CVSS 4.3). 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 initia

How urgent is CVE-2022-3464?

Priority 28/100. No elevated risk signals yet.

Software pages

PHP vulnerabilities

Related CVEs

CVE-2020-18890 CRITICAL 9.8 DOWNGRADE Rmote Code Execution (RCE) vulnerability in puppyCMS v5.1 due to insecure permissions, which could let a remot
CVE-2020-18889 MEDIUM 6.5 DOWNGRADE Cross Site Request Forgery (CSRF) vulnerability in puppyCMS v5.1 that can change the admin's password via /adm
CVE-2020-18888 HIGH 7.5 DOWNGRADE Arbitrary File Deletion vulnerability in puppyCMS v5.1 allows remote malicious attackers to delete the file/fo

References

← Back to latest CVEs