CVE-2023-2533
A Cross-Site Request Forgery (CSRF) vulnerability has been identified in PaperCut NG/MF, which, under specific conditions, could potentially enable an attacker to alter security settings or execute arbitrary code. This could be exploited if the target is an admin with a current login session. Exploiting this would typically involve the possibility of deceiving an admin into clicking a specially crafted malicious link, potentially leading to unauthorized changes.
do firstUpgrade to a fixed release: 21.2.12, 20.1.8.
Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.
Cloudflare · 1 rule (Block) · since 11 Aug 2025
- PaperCut NG/MF - Remote Code Execution - CVE:CVE-2023-2533 · Cloudflare Managed Ruleset
Also consider: patch · enable the vendor rule in block mode · SameSite cookies · CSRF tokens
Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2023-2533 being exploited?
Yes. CVE-2023-2533 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2023-2533?
CVE-2023-2533 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2023-2533?
Yes. A fix has been recorded for CVE-2023-2533. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2023-2533 affect?
CVE-2023-2533 affects papercut:papercut_mf, papercut:papercut_ng. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 22.0.10 and < 2.1.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 26 Jul 2025 (SSVC 2.0.3).
timeline
- 20 Jun 2023Published
- 26 Jul 2025CISA SSVC assessment: exploitation active · 767 days (about 2 years) later
- 28 Jul 2025Added to CISA KEV (exploited in the wild) · 2 days later
- 18 Aug 2025CISA remediation due date (US federal agencies) · 21 days later
- 21 Oct 2025CVE record last updated · 65 days (about 2 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkfluidattacks.com /advisories/arcangel/
- Linkpapercut.com /kb/Main/SecurityBulletinJune2023
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-2533
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.