This vulnerability potentially allows unauthorized write operations which may lead to remote code execution. An attacker must already have authenticated admin access and knowledge of both an internal system identifier and details of another valid user to exploit this.
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Papercut_mf | Papercut | * | 20.1.10 (excluding) |
| Papercut_mf | Papercut | 21.0.0 (including) | 21.2.14 (excluding) |
| Papercut_mf | Papercut | 22.0.0 (including) | 22.1.5 (excluding) |
| Papercut_mf | Papercut | 23.0.1 (including) | 23.0.7 (excluding) |
| Papercut_ng | Papercut | * | 20.1.10 (excluding) |
| Papercut_ng | Papercut | 21.0.0 (including) | 21.2.14 (excluding) |
| Papercut_ng | Papercut | 22.0.0 (including) | 22.1.5 (excluding) |
| Papercut_ng | Papercut | 23.0.1 (including) | 23.0.7 (excluding) |