dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-22556

HIGH · 7.1 CVSS v3.1 Published 2025-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in WP CMS Ninja Norse Rune Oracle Plugin norse-runes-oracle allows Cross Site Request Forgery.This issue affects Norse Rune Oracle Plugin: from n/a through <= 1.4.2.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Norse Rune Oracle WordPress plugin (versions <= 1.4.2) allows remote attackers to induce authenticated administrators to perform unintended state-changing actions (such as modifying plugin settings) by tricking them into visiting malicious pages. The plugin lacks proper anti-CSRF token validation on its administrative functions.

MitigationImplement WordPress nonces on all form submissions and AJAX requests that perform state-changing operations, and verify these nonces server-side before processing. Users should update to a patched version when available or remove the plugin until fixed.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin is installed
    Check if the 'norse-rune-oracle' folder exists in wp-content/plugins/ directory
    Affected if The plugin folder is present in the plugins directory
  2. Identify installed version
    Open the main plugin file (usually norse-rune-oracle.php) and locate the Version header in the plugin comment block
    Affected if Version is 1.4.2 or lower
  3. Check if plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify if Norse Rune Oracle is activated
    Affected if Plugin is active and accessible to administrators
  4. Verify admin functions exist
    Check plugin admin menu items or capabilities - the vulnerability affects administrative functions that perform state-changing operations
    Affected if Plugin provides admin settings or configuration panels that modify plugin data
  5. Inspect form submissions for nonce protection
    Examine plugin PHP source code for form handling in admin area - look for wp_nonce_field, wp_verify_nonce, or check_admin_referer calls on state-changing forms
    Affected if Forms that modify settings lack WordPress nonce verification logic

User is affected if the Norse Rune Oracle plugin version is 1.4.2 or lower and it provides administrative functions that modify plugin settings without proper CSRF token validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces on all form submissions and AJAX requests that perform state-changing operations, and verify these nonces server-side before processing. Users should update to a patched version when available or remove the plugin until fixed.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22556 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22556 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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