Is Login Page Editor safe to use?

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

Which versions of Login Page Editor are vulnerable?

Known issues on record (newest first): Cross-site request forgery (CSRF) (1.2 and older). The full list with sources is on this page.

What should I do if my Login Page Editor is out of date?

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

Is Login Page Editor safe? Known vulnerabilities and latest version

Status: Closed 2026-01-21
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 login-page-editor && wp plugin delete login-page-editor

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-1088 · published 2026-01-24

Cross-site request forgery (CSRF) in Login Page Editor (1.2 and older)

Affected: 1.2 and older
Fixed in: unknown
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Login Page Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing nonce validation on the devotion_loginform_process() AJAX action. This makes it possible for unauthenticated attackers to update the plugin's login page settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

NVD CVE-2026-1088 Wordfence advisory Plugin source

Recent activity

2026-01-21 — closed on wordpress.org (Security Issue).
2026-01-24 — Cross-site request forgery (CSRF) disclosed (CVE-2026-1088), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for Login Page Editor (login-page-editor) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site request forgery (CSRF) (1)

Where this data comes from

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

← Check another plugin · Free hacked-site scan