Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-22556: Cross-Site Request Forgery (CSRF) in WP CMS Ninja Norse Rune Oracle Plugin

0
Unknown
VulnerabilityCVE-2025-22556cvecve-2025-22556
Published: Tue Jan 07 2025 (01/07/2025, 14:57:15 UTC)
Source: CVE Database V5
Vendor/Project: WP CMS Ninja
Product: Norse Rune Oracle Plugin

Description

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 01:25:49 UTC

Technical Analysis

CVE-2025-22556 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the WP CMS Ninja Norse Rune Oracle Plugin, a WordPress plugin designed to provide Norse rune oracle functionalities. The vulnerability exists in versions up to and including 1.4.2. CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a forged request to the web application, causing the application to perform unwanted actions on behalf of the user. In this case, the plugin lacks adequate CSRF protections such as nonce verification or proper request method enforcement, allowing attackers to craft malicious web pages that, when visited by an authenticated WordPress user, can trigger unauthorized plugin actions. The vulnerability affects the integrity of the plugin’s operations and potentially the availability of its services, as unauthorized changes or commands could be executed. No CVSS score has been assigned yet, and no public exploits are known. The vulnerability was published on January 7, 2025, by Patchstack. The plugin’s niche nature limits the attack surface but does not eliminate risk, especially in environments where the plugin is actively used. Since the plugin operates within WordPress, the vulnerability inherits the exposure of WordPress sites that use this plugin. The lack of patch links suggests that a fix may not yet be available, emphasizing the need for immediate mitigation steps.

Potential Impact

The primary impact of this CSRF vulnerability is the potential for unauthorized actions to be performed within the Norse Rune Oracle Plugin by attackers leveraging authenticated users’ sessions. This can lead to unauthorized configuration changes, data manipulation, or disruption of plugin functionality, affecting the integrity and availability of the affected WordPress site components. While confidentiality impact is limited, the integrity and availability risks can affect site reliability and user trust. Organizations using this plugin, especially those with multiple authenticated users or administrative roles, face increased risk of privilege abuse or site defacement. The lack of known exploits reduces immediate risk, but the vulnerability remains exploitable in targeted attacks. Given WordPress’s widespread use, sites that rely on this plugin for niche functionality could be disrupted, potentially impacting business operations, user experience, or content management. The vulnerability could also be leveraged as part of a larger attack chain to escalate privileges or pivot within compromised environments.

Mitigation Recommendations

1. Immediately check for and apply any available updates or patches from WP CMS Ninja addressing this vulnerability. 2. If no patch is available, temporarily disable the Norse Rune Oracle Plugin to eliminate exposure. 3. Implement manual CSRF protections by adding nonce verification tokens to all plugin forms and AJAX requests that perform state-changing operations. 4. Restrict sensitive plugin actions to POST requests only and reject GET requests for such operations. 5. Limit the number of users with administrative or high-privilege roles who can access the plugin’s functionality. 6. Monitor web server and WordPress logs for unusual POST requests or suspicious activity targeting the plugin endpoints. 7. Educate users to avoid clicking on suspicious links while authenticated to WordPress sites. 8. Consider deploying a Web Application Firewall (WAF) with custom rules to detect and block CSRF attack patterns targeting the plugin. 9. Regularly audit installed plugins for security vulnerabilities and remove unnecessary or unmaintained plugins.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-01-07T10:23:24.211Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd75f5e6bfc5ba1df088bf

Added to database: 4/1/2026, 7:45:57 PM

Last enriched: 4/2/2026, 1:25:49 AM

Last updated: 4/4/2026, 8:21:10 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses