Is Continually safe to use?

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

Which versions of Continually are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (4.3.1 and older). The full list with sources is on this page.

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

Take a backup, then update it from Dashboard > Updates (or run wp plugin update continually). 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 · continually · data as of 2026-11-04

Is Continually safe? Known vulnerabilities and latest version

Status: Closed 2026-05-04
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 continually && wp plugin delete continually

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.4 CVE-2026-6813 · published 2026-05-12

Stored cross-site scripting (XSS) in Continually (4.3.1 and older)

Affected: 4.3.1 and older
Fixed in: unknown
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Continually plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 4.3.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

NVD CVE-2026-6813 Wordfence advisory Plugin source

Recent activity

2026-05-04 — closed on wordpress.org (Security Issue).
2026-05-12 — Stored cross-site scripting (XSS) disclosed (CVE-2026-6813), fix version not stated.

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

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/continually (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/continually"><img src="https://laskyr.com/plugins/continually/badge.svg" alt="Continually vulnerability status"></a>

← Check another plugin · Free hacked-site scan