Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:LSummary
CVE-2024-1883 is a medium-severity Improper Neutralization of Equivalent Special Elements (CWE-76) vulnerability in Papercut Papercut Mf. Its CVSS base score is 6.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked in the top 0.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
This is a reflected cross-site scripting vulnerability affecting the PaperCut NG/MF application server. The weakness, tracked under CWE-79 and CWE-76, allows an attacker to supply a script within a URL that executes in the victim's browser context when the link is visited.
An unauthenticated remote attacker can exploit the flaw by crafting a malicious URL and enticing an unsuspecting user to click it. Successful exploitation results in limited loss of confidentiality, integrity, or availability, consistent with the CVSS 6.3 rating that requires user interaction but no prior authentication.
The associated EPSS score rose from lower values to a peak of 0.4524 on 2025-12-11 before receding to the current 0.1126, indicating a period of increased exploitation interest after disclosure. PaperCut's March 2024 security bulletin provides official guidance on the issue.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-17608
Vulnerability Data
This is a reflected cross site scripting vulnerability in the PaperCut NG/MF application server. An attacker can exploit this weakness by crafting a malicious URL that contains a script. When an unsuspecting user clicks on this malicious link, it could…
more
potentially lead to limited loss of confidentiality, integrity or availability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.2V1.3.2
Mitigating Controls (NIST 800-53 r5) AI
SA-11 requires developer testing and evaluation that can discover failures to neutralize equivalent special elements.
SI-10 requires validation of information inputs, directly stopping incomplete neutralization of equivalent special elements.
Output filtering can catch or sanitize unneutralized script content before it is served to users.
SA-8 mandates security engineering principles such as complete input validation and sanitization that cover equivalent special-element forms.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require consistent neutralization of all equivalent special elements during input validation and sanitization.
Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect incomplete neutralization but does not prevent the weakness itself.
Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.
Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.
Secure development life cycle mandates input validation and neutralization of all equivalent special elements.
Application security requirements include rules for handling special characters and equivalent encodings.
Secure system architecture principles require consistent canonicalization and neutralization of equivalent inputs.