Is Assistio safe to use?

Laskyr does not give safety verdicts. Assistio is closed on wordpress.org. Closed on 2026-06-18 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep Assistio on the latest version and remove it if you do not use it.

Which versions of Assistio are vulnerable?

Known issues on record (newest first): Missing authorization check (1.1.2 and older). The full list with sources is on this page.

What should I do if my Assistio is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update assistio). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · assistio · data as of 2026-11-04

Is Assistio safe? Known vulnerabilities and latest version

Status: Closed 2026-06-18
Known issues on record: 1
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate assistio && wp plugin delete assistio

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 1 record(s) do not state which versions are affected.

medium 4.3 CVE-2026-8614 · published 2026-06-24

Missing authorization check in Assistio (1.1.2 and older)

Affected: 1.1.2 and older
Fixed in: unknown
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Assistio plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check and missing nonce verification on the assistio_plugin_delete_assistio_settings() function in versions up to, and including, 1.1.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete the plugin's options including the critical 'assistiobot_oauth_settings' option, which disrupts the plugin's integration with the Assistio bot service.

NVD CVE-2026-8614 Wordfence advisory Plugin source

Recent activity

2026-06-18 — closed on wordpress.org (Security Issue).
2026-06-24 — Missing authorization check disclosed (CVE-2026-8614), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for Assistio (assistio) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/assistio (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/assistio"><img src="https://laskyr.com/plugins/assistio/badge.svg" alt="Assistio vulnerability status"></a>

← Check another plugin · Free hacked-site scan