Login Screen ManagerWordPress extension · Nazmulhossainnihal
CVE-2023-47182
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) leading to a Stored Cross-Site Scripting (XSS) vulnerability in Nazmul Hossain Nihal Login Screen Manager plugin <= 3.5.2 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 · moderate confidenceA CSRF vulnerability in the Login Screen Manager plugin <= 3.5.2 allows attackers to trick authenticated administrators into submitting malicious requests that store XSS payloads. The stored scripts execute when other users access the affected login screen configuration pages, potentially compromising administrator sessions and stealing credentials.
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
Login Screen ManagerWordPress extension
<= 3.5.2CVSS 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 Login Screen Manager plugin is installedAccess your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Login Screen Manager' by Nazmulhossainnihal in the list.Affected if The plugin is present in the plugins list and is active
-
Determine the installed plugin versionIn the Plugins page, click on the plugin name or view details to find the version number displayed under the plugin name. Compare it to the affected range: any version <= 3.5.2 is vulnerable.Affected if The installed version is 3.5.2 or lower
-
Inspect configuration forms for CSRF protectionNavigate to the plugin's settings page (Login Screen Manager settings). View the page source (right-click > View Page Source) and search for 'nonce' or '_wp' tokens in the form HTML. A vulnerable form will lack these CSRF token fields.Affected if The configuration forms do not contain nonce tokens or _wp security parameters in their HTML
-
Check for stored XSS payloads in configurationAccess the plugin's login screen configuration pages. Examine any fields that store custom text, messages, or HTML (such as welcome messages, labels, or custom CSS). Look for unexpected script tags, iframe elements, or encoded JavaScript.Affected if Any stored scripts or suspicious HTML/JS code is found in the login screen configuration fields
-
Review admin activity for suspicious form submissionsCheck your WordPress activity logs, audit logs, or security plugin logs for any unexpected POST requests to the Login Screen Manager admin pages, especially from the current administrator account.Affected if There are unexplained form submissions to the plugin settings from your admin account
Your environment is affected if the Login Screen Manager plugin version is 3.5.2 or lower, and the plugin's configuration forms lack CSRF token protection.
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 Login Screen Manager plugin to a version beyond 3.5.2. If no update is available, disable the plugin until a patch is released, or manually implement CSRF tokens (nonces) on all configuration forms and add proper input sanitization/output encoding for all user-supplied values.
Fix this in Login Screen Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47182 — 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-47182 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