CVE-2025-26547
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 nagarjunsonti My Login Logout Plugin my-loginlogout allows Stored XSS.This issue affects My Login Logout Plugin: from n/a through <= 2.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the My Login Logout WordPress plugin (versions <= 2.4) by developer nagarjunsonti allows authenticated attackers to craft malicious requests that inject Stored XSS payloads into the plugin's settings or user-facing elements due to missing or improper nonce validation on form submissions and AJAX actions.
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.
-
Confirm plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'My Login Logout' by nagarjunsonti. Check the version number displayed below the plugin name.Affected if The plugin is installed and the version is 2.4 or lower.
-
Inspect plugin for missing nonce verificationAccess the plugin files via FTP or file manager. Locate the main PHP file (usually my-login-logout.php or similar) and search for form handling functions. Look for the absence of 'wp_verify_nonce' or 'check_admin_referer' calls in functions that process form submissions or AJAX requests.Affected if Form processing functions lack nonce validation code.
-
Check plugin settings page for CSRF-vulnerable formsNavigate to the plugin's settings page in WordPress admin (usually under Settings > My Login Logout or similar). View the page source and check if the forms contain a nonce field (wpnonce or similar). Try submitting a form without the nonce token to see if it succeeds.Affected if Forms lack a nonce field or accept submissions without valid nonce verification.
-
Test for stored XSS via plugin settingsSubmit a test payload containing HTML/script tags (such as <img src=x onerror=alert(1)>) into the plugin's text input fields on the settings page. Then view the frontend or relevant output area to see if the payload executes without sanitization.Affected if The submitted payload executes as JavaScript when displayed, indicating stored XSS.
A user is affected if the My Login Logout plugin (versions 2.4 or lower) is installed, its forms lack nonce verification, and unsanitized input can be stored and rendered as executable code.
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 form submissions and AJAX hooks, add proper input sanitization for all user-supplied data, and ensure output escaping is applied when displaying any stored data to prevent the XSS vector.
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26547 — 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-26547 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