CVE-2022-4881: A vulnerability was found in CapsAdmin PAC3

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

pac3: upgrade to 2022-07-13. Exact commands for each OS are on this page.

Q: Is CVE-2022-4881 being exploited?

CVE-2022-4881 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-4881 affect?

CVE-2022-4881 affects pac3. Severity is medium (CVSS 4.3). A vulnerability was found in CapsAdmin PAC3. It has been rated as problematic. Affected by this issue is some unknown functionality of the file lua/pac3/core/shared/http.lua. The manipulation of the argument url leads to cross site scriptin

Q: How urgent is CVE-2022-4881?

Priority 27/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

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

A vulnerability was found in CapsAdmin PAC3. It has been rated as problematic. Affected by this issue is some unknown functionality of the file lua/pac3/core/shared/http.lua. The manipulation of the argument url leads to cross site scripting. The attack may be launched remotely. The patch is identified as 8fc9e12dfa21d757be6eb4194c763e848b299ac0. It is recommended to apply a patch to fix this issue. VDB-217646 is the identifier assigned to this v

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.6% (top 52%)
CISA exploited list	No
Weakness	CWE-79
Published	2023-01-08
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: pac3 project

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

Am I affected?

Timeline

2023-01-08 13:15 UTCPublished CVE record published
2026-06-17 05:22 UTCUpdated Record last modified

pac3 project pac3 UPGRADE

Affected: < 2022-07-13

Fixed in: 2022-07-13

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 2022-07-13 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pac3

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-4881?

pac3: upgrade to 2022-07-13. Exact commands for each OS are on this page.

Is CVE-2022-4881 being exploited?

CVE-2022-4881 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-4881 affect?

CVE-2022-4881 affects pac3. Severity is medium (CVSS 4.3). A vulnerability was found in CapsAdmin PAC3. It has been rated as problematic. Affected by this issue is some unknown functionality of the file lua/pac3/core/shared/http.lua. The manipulation of the argument url leads to cross site scriptin

How urgent is CVE-2022-4881?

Priority 27/100. No elevated risk signals yet.

References

← Back to latest CVEs