Custom Login Page \| Temporary Users \| Rebrand Login \| Login CaptchaWordPress extension · Featherplugins
CVE-2023-46777
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Custom Login Page | Temporary Users | Rebrand Login | Login Captcha plugin <= 1.1.3 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · low confidenceCross-Site Request Forgery (CSRF) vulnerability in the Custom Login Page plugin allows attackers to trick authenticated administrators into unknowingly submitting malicious requests to the WordPress site, potentially performing unauthorized actions like modifying login settings or creating malicious user accounts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Custom Login Page \| Temporary Users \| Rebrand Login \| Login CaptchaWordPress extension
<= 1.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder containing 'custom-login-page' or 'featherplugins' in the name, or view the installed plugins list in the WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists in the plugins directory or the plugin appears in the WordPress admin plugin list
-
Identify the installed plugin versionOpen the main plugin PHP file (usually found in the plugin folder as index.php, main.php, or similar) and locate the version header in the plugin comment block at the top, or check the version column in Plugins > Installed Plugins in WordPress adminAffected if The version displayed is 1.1.3 or lower (any version <= 1.1.3)
-
Confirm the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify the Custom Login Page plugin shows as 'Active' under the plugin nameAffected if The plugin status is Active - only active installations can be exploited via CSRF
Your site is affected if the Featherplugins Custom Login Page plugin is installed and active at version 1.1.3 or lower, allowing authenticated administrators to be tricked into unknowingly submitting malicious requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to the latest version beyond 1.1.3 which should include proper anti-CSRF token validation for state-changing requests; alternatively, implement referrer checking and ensure all form submissions and admin actions include valid CSRF tokens.
Fix this in Custom Login Page \| Temporary Users \| Rebrand Login \| Login Captcha
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-46777 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data