CVE-2025-49425
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 Adrian Hanft Konami Easter Egg konami-easter-egg allows Stored XSS.This issue affects Konami Easter Egg: from n/a through <= v0.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 confidenceA CSRF vulnerability in the konami-easter-egg WordPress plugin (<= v0.4) allows attackers to inject stored XSS payloads by tricking authenticated administrators into submitting malicious requests. The lack of anti-CSRF tokens on state-changing operations enables attackers to forge requests that persist malicious scripts into the application, which then execute when other users view the affected content.
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.
-
Verify if konami-easter-egg plugin is installedNavigate to WordPress admin > Plugins or use 'wp plugin list' CLI command to list installed pluginsAffected if The konami-easter-egg plugin appears in the installed plugins list
-
Determine the installed version of konami-easter-eggCheck the plugin header in the main plugin file (usually wp-content/plugins/konami-easter-egg/konami-easter-egg.php) or use 'wp plugin get konami-easter-egg' CLI commandAffected if The version reported is 0.4 or lower (e.g., 0.4, 0.3, 0.2, 0.1)
-
Inspect plugin forms for missing CSRF tokensExamine the plugin PHP source code for state-changing operations (form submissions, settings updates, AJAX actions) and verify whether each uses wp_nonce_field() or check_admin_referer()Affected if Any state-changing form or action lacks WordPress nonce verification (no nonce field and no referer check)
-
Search for suspicious stored content in the databaseQuery the wp_options table or any custom plugin tables for stored values that may contain script tags, event handlers (onload, onerror, etc.), or encoded JavaScript payloadsAffected if Unexpected script tags or JavaScript code is found stored in plugin-related database entries
A user is affected if the konami-easter-egg plugin version is 0.4 or lower AND the plugin performs state-changing operations without CSRF protection, or if malicious scripts have already been stored in the database.
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 on all form submissions and state-changing actions, and apply proper output encoding/escaping when rendering user-supplied data to prevent the stored XSS.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49425 — 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-49425 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