CVE-2023-2533
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA CSRF vulnerability in PaperCut NG/MF allows attackers to perform unauthorized actions by tricking authenticated administrators into clicking malicious links. The attack can potentially alter security settings or execute arbitrary code on the affected system through the compromised admin session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 20.1.8>= 21.0.0, < 21.2.12>= 22.0.0, < 22.1.1< 20.1.8>= 21.0.0, < 21.2.12>= 22.0.0, <= 22.1.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed PaperCut versionLog into the PaperCut admin web interface and navigate to the About or Version section, typically found under Help > About or the main dashboard. Alternatively, check the installation directory for a version file or check server logs for startup version information.Affected if The installed version matches one of the vulnerable ranges: PaperCut MF versions < 20.1.8, >= 21.0.0 and < 21.2.12, or >= 22.0.0 and < 22.1.1; PaperCut NG versions < 20.1.8, >= 21.0.0 and < 21.2.12, or >= 22.0.0 and <= 22.1.1
-
Verify admin web interface is network accessibleConfirm the PaperCut admin interface (typically on ports 9191 or 8090) is reachable from network segments where untrusted users could originate malicious requests. Check firewall rules and network ACLs.Affected if The admin interface is exposed to users or networks beyond trusted administrators, increasing the likelihood of a successful CSRF attack via social engineering.
-
Check for SameSite cookie attribute configurationInspect the PaperCut server configuration files (commonly in the server's config directory or web.xml) for SameSite cookie attributes. Alternatively, use browser developer tools to inspect the session cookie Set-Cookie headers when logging into the admin interface.Affected if No SameSite attribute is set on session cookies, or SameSite is set to None without Secure flag, indicating missing CSRF protection.
-
Review state-changing admin actions for CSRF token presenceUse browser developer tools to capture a request when making a state-changing admin action (such as modifying user settings, adding a printer, or changing security options). Examine the request headers and body for anti-CSRF token parameters.Affected if No anti-CSRF token parameter is present in POST/PUT requests that modify system configuration or security settings, leaving the application vulnerable to forged requests.
If the installed version falls within the affected ranges AND the admin interface is network-accessible to untrusted users AND SameSite cookies are not configured AND no anti-CSRF tokens are present in state-changing requests, the environment is vulnerable to CVE-2023-2533.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped20.1.821.2.1222.1.1
Implement anti-CSRF tokens on all state-changing operations, validate Origin/Referer headers, and configure SameSite cookie attributes. Additionally, educate administrators about avoiding clicking untrusted links.
PaperCut Mf: 20.1.8, 21.2.12, or 22.1.2+ | PaperCut Ng: 20.1.8, 21.2.12, or 22.1.2+
- 1. Identify the currently installed PaperCut NG/MF version from the admin interface (Help > About) or server logs
- 2. Determine which version branch your installation falls into (20.x, 21.x, or 22.x)
- 3. Download the appropriate fixed version from the official PaperCut website: 20.1.8 or later for 20.x branch, 21.2.12 or later for 21.x branch, 22.1.2 or later for 22.x branch
- 4. Before upgrading, backup the PaperCut data directory and any custom configurations
- 5. Stop the PaperCut service or application server
- 6. Install the new version following the standard PaperCut upgrade procedure documented at www.papercut.com
- 7. Start the PaperCut service and verify the admin interface is accessible
- 8. Confirm the version number in Help > About matches the expected fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2533 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-2533 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data