Safeguard
Vulnerability Analysis•

CVE-2022-42884: Medium Access Flaw in WIP Custom Login Plugin

CVE-2022-42884 is a medium (5.4) missing authorization bug in the WIP Custom Login WordPress plugin up to version 1.2.7. Update to version 1.2.8 or later.

Safeguard Security Team
3 min read

CVE-2022-42884 is a medium severity (CVSS 5.4) missing authorization flaw in the WIP Custom Login plugin for WordPress, versions up to and including 1.2.7. Update to 1.2.8 or later. Check your installed version and apply the update through your normal change process.

What's affected

The record lists WIP Custom Login from ThemeinProgress, from the first release through 1.2.7. Patchstack gives the patched version as 1.2.8. Patchstack gives the required privilege as Subscriber.

The record scores it 5.4 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N. Patchstack labels its own priority Medium. The weakness class is CWE-862 (Missing Authorization).

How to check if you're exposed

Start with an inventory. If you manage the site with WP-CLI, this lists every plugin with its version and whether an update is waiting:

wp plugin list --fields=name,status,version,update

Look for the folder wip-custom-login. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Plugins screen in the dashboard and read the version shown under the name. Version 1.2.7 or lower is affected. Version 1.2.8 or later is patched.

Check staging copies, old multisite subsites and inactive plugins too. A deactivated plugin is still on disk, and some of these bugs are reachable through files that load even when the plugin is switched off, so deactivation alone is not a fix. Delete what you do not use.

What to do now

  1. Update WIP Custom Login to 1.2.8 or a newer release.
  2. Review the site's user list and remove accounts you do not recognise.
  3. Turn on automatic updates for the plugin so the next fix lands without a ticket.

Why it matters

A custom login plugin sits near the most sensitive part of a WordPress site: the login screen and its settings. The record describes missing authorization checks, and the Patchstack URL says multiple issues of that kind exist. A Subscriber can reach functions that should be limited.

The score is medium, with low confidentiality and integrity impact and none on availability. Patchstack ranks its own priority Medium, one step above several of its neighbours in this series. Because the plugin controls how people sign in, review its settings after updating: look for changed redirects, logos, links or custom code fields.

The record does not list which functions are affected, so I do not name any. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.

Quick check

Why check the plugin settings after updating?

Updating removes the flaw going forward but does not undo changes someone may already have made. A quick review of the login customisation settings is cheap.

What is the fixed version?

Patchstack lists 1.2.8.

Sources

Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.