CVE-2025-25149
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 Danillo Nunes Login-box login-box allows Stored XSS.This issue affects Login-box: from n/a through <= 2.0.4.
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 · high confidenceThe Login-box WordPress plugin <= 2.0.4 contains a Cross-Site Request Forgery (CSRF) vulnerability that enables Stored XSS attacks. An attacker can exploit this by tricking an authenticated administrator into visiting a malicious page, causing the browser to submit a crafted request that injects malicious scripts into the login-box settings. These scripts are then stored on the server and executed when other users view the affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Identify if Login-box plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Login-box' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'login-box' or similar.Affected if The plugin is present in the WordPress installation
-
Determine installed plugin versionIn WordPress admin plugins list, click on the plugin to view details and find the version number. Or inspect the plugin's main PHP file header for 'Version:' tag.Affected if The version is 2.0.4 or lower
-
Check plugin settings forms for CSRF protectionAccess the plugin settings page (usually under Settings or a dedicated Login-box menu). View the page source of any form elements and check if they contain a nonce field (wpnonce, _wpnonce, or similar) in the HTML.Affected if The forms lack nonce/token fields or the nonce verification is missing from the form processing code
-
Verify stored XSS potential in settingsIf you have admin access, examine the plugin's settings fields where user input is saved. Check if the plugin stores and later displays these values without proper sanitization.Affected if Settings values are output without escaping or sanitization functions (such as esc_html, esc_attr)
The environment is affected if the Login-box plugin version is 2.0.4 or lower and the plugin settings lack CSRF nonce protection on its forms.
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 dataImplement anti-CSRF tokens (nonces) on all state-changing forms and admin actions, combined with proper input sanitization and output encoding to prevent XSS execution.
- 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-2025-25149 — 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-2025-25149 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