CVE-2025-31459
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 PasqualePuzio Login Alert login-alert allows Stored XSS.This issue affects Login Alert: from n/a through <= 0.2.1.
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 confidenceThe Login Alert WordPress plugin has a CSRF vulnerability that allows attackers to inject Stored XSS payloads. Attackers can trick authenticated administrators into visiting malicious pages, causing the admin's browser to send forged requests that inject malicious scripts into the plugin's stored alert data. When other users view the affected content, the XSS executes.
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 Login Alert plugin installationNavigate to WordPress admin > Plugins > Installed Plugins and look for 'Login Alert' or check the plugin files in /wp-content/plugins/ for a login-alert directory. Check the plugin main file header for the Version number.Affected if The plugin is installed and no patch has been applied by the vendor.
-
Verify plugin activation statusIn WordPress admin > Plugins, confirm whether Login Alert is currently activated.Affected if Plugin is activated and contains the unpatched CSRF/XSS vulnerability.
-
Inspect stored alert configurations for XSS payloadsAccess the plugin settings (usually under Settings > Login Alert or similar). Examine all alert message fields, especially those that accept user input for display to other users. Check the WordPress database directly if needed: SELECT * FROM wp_options WHERE option_name LIKE '%login_alert%';Affected if Any alert fields contain unexpected HTML, script tags, or javascript: URLs that were not intentionally entered by an administrator.
-
Review plugin source code for nonce implementationExamine the plugin's PHP files, specifically form handlers and AJAX actions. Look forwp_nonce_field(), wp_nonce_verify(), or check_admin_referer() calls on state-changing operations. Files to inspect include the main plugin file and any admin/settings files.Affected if State-changing forms or AJAX actions lack CSRF token validation, indicating the vulnerability is present.
You are affected if the Login Alert plugin is installed and activated, the stored alert data contains suspicious script injections, or the plugin code lacks CSRF nonce validation 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 WordPress nonces (anti-CSRF tokens) on all state-changing forms and AJAX actions, add proper input validation and output escaping for all user-supplied data in login alerts.
- Consultation2.0 h
- Implementation6.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31459 — 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-31459 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