HomeWordPress vulnerabilitiesOpenStation
OpenStation vulnerabilities
OpenStation has 2 known vulnerabilities in this database. The most recent published record is dated 30 Oct 2026.
- Known vulnerabilities
- 2
- Active installs
- 1,000+
- Latest version
- 1.1.20
- Last updated
- 13 Nov 2026
- Most recent
- 30 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-109592 | Medium 4.3 | Up to 1.1.16 | Fixed in a later version (latest 1.1.20) | 30 Oct 2026 |
| Broken access control CVE-2026-19775 | Medium 4.3 | Up to 1.1.7 | Fixed in a later version (latest 1.1.20) | 25 Sep 2026 |
Read the published descriptions
- CVE-2026-109592, 30 Oct 2026
- 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. CVE record
- CVE-2026-19775, 25 Sep 2026
- 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.7. 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 custom-level access and above, to read the title, status, date, permalink, and a 300-character content excerpt of any private, draft, pending, or future post, as well as the content and AI-moderation verdicts of unapproved and spam comments. Any authenticated user with the 'read' capability can self-enable the required AI feature by visiting the /openstation/ portal and toggling their own ai.enabled setting via the POST /desktop-mode/v1/os-settings endpoint, removing any practical barrier to exploitation. CVE record
What to do if you run OpenStation
If you run OpenStation, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new OpenStation vulnerabilities
Free. We email you when a new vulnerability is published for OpenStation, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.