CVE-2026-109592: OpenStation (WordPress plugin) · Missing Authorization
Affects OpenStation (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 30 Oct 2026, 18:33 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 4.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wordpressdotorgOpenStation – Admin Dashboard Notes, Custom Dashboard, AI Assistant & PWA | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor advisory for updates. Until a fix is available, consider restricting plugin usage to trusted users only and disabling or removing the OpenStation plugin if orphaned placements exist or if subscriber-level users do not require access. Since the vulnerability requires self-enabling via an AJAX endpoint accessible to all roles, limiting access to this endpoint or applying custom authorization checks may mitigate risk.
Description
The OpenStation: Desktop Windows, Dock & Virtual Desktops for WP Admin plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.1.16. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify arbitrary other users' placement rows (position, sort order, parent folder, and meta) and read serialized metadata — including title, permalink, and post status — of the entities those orphaned placements reference. Exploitation requires at least one orphaned placement to exist — a state produced naturally by the plugin's own trash cascade, which marks a parent folder as trashed while leaving child placements' parent_id intact — and the attacker must first self-enable OpenStation via the save-openstation AJAX endpoint, which requires only the 'read' capability held by every default WordPress role. This was also independently found by the OpenStation team.
References
- wordfence.com/threat-intel/vulnerabilities/id/a62e499d-6520-4bad-963a-ff7619daa5f8?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/desktop-mode/tags/1.1.13/includes/desktop-files/store.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/desktop-mode/tags/1.1.13/includes/desktop-files/rest.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/desktop-mode/tags/1.1.13/includes/desktop-files/folders-store.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/desktop-mode/tags/1.1.13/includes/desktop-files/rest.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3761843%40desktop-mode&new=3761843%40desktop-mode (opens in a new tab)