Skip to main content
VulnerabilityPublished Updated

CVE-2026-42562: alextselegidis plainpad · Improper Privilege Management

Affects alextselegidis plainpadSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 1.1.1 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.1.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade plainpad and alextselegidis/plainpad to 1.1.1.

Affected software

ProductAffectedFixed in
alextselegidisplainpadAffected
  • <1.1.1
Fixed in
  • 1.1.1
GitHubalextselegidis/plainpadpkg:github/alextselegidis/plainpadOther threatsAffected
  • <1.1.1
Fixed in
  • 1.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Plainpad to version 1.1.1 or later, where this privilege escalation vulnerability has been patched. Since the vendor has released a fixed version, applying this official update is the recommended remediation. No additional mitigations are indicated.

Description

Plainpad is a self hosted note taking app. Prior to version 1.1.1, Plainpad allows a low-privilege authenticated user to self-escalate to administrator by submitting admin=true in PUT /api.php/v1/users/{id}. The endpoint directly persists the admin attribute from user input, and the escalated account can immediately access admin-only routes. This issue has been patched in version 1.1.1.

References

Community reviews

Loading reviews…