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

CVE-2025-26748

HIGH · 8.1 CVSS v3.1 Published 2025-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 looswebstudio Arkhe arkhe allows PHP Local File Inclusion.This issue affects Arkhe: from n/a through <= 3.12.0.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Arkhe WordPress theme enables attackers to trigger a PHP Local File Inclusion (LFI) flaw, potentially allowing unauthorized file access and possibly remote code execution through inclusion of arbitrary PHP files.

MitigationUpdate to the latest patched version of Arkhe theme once available, and implement CSRF nonce tokens on all state-changing operations plus validate and sanitize all file inclusion paths to prevent directory traversal.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Locate Arkhe theme installation
    Check the wp-content/themes/ directory for the arkhe folder. If present, open style.css in that folder and look for the 'Version:' declaration in the theme header comment to identify the installed version.
    Affected if The theme is installed and the version cannot be confirmed as patched, or the version is unknown.
  2. Identify file inclusion functionality
    Search theme PHP files (particularly in arkhe/inc/, arkhe/functions/, or similar directories) for functions that use include, require, include_once, or require_once with user-controlled or insufficiently sanitized variables. Look for patterns like 'include($file)' or 'require($_GET[..])'.
    Affected if The theme contains file inclusion code that accepts variable input without strict path validation.
  3. Verify CSRF protection on state-changing actions
    Inspect theme PHP files that handle settings, uploads, or file operations. Search for the presence of nonce verification using wp_verify_nonce or check_admin_referer. If these checks are missing on functions that perform file operations, CSRF protection is absent.
    Affected if State-changing operations (especially those involving file inclusion or settings) lack nonce token validation.
  4. Check for directory traversal vulnerabilities
    Examine any file inclusion code found for path traversal protections. Look for whether the code validates that paths stay within allowed directories (for example, checking for '../' patterns or using realpath() to resolve paths).
    Affected if File inclusion allows traversal sequences (..%2F or ..%252F URL-encoded) or lacks directory boundary checks.
  5. Compare version to affected releases
    Since no specific version range is provided, check the official WordPress theme repository or the theme developer's changelog for Arkhe to determine if versions prior to the patch date are in use.
    Affected if The installed version predates the CVE publication date (2025) and no patch has been applied.

The environment is affected if the Arkhe theme is installed with a version predating the CVE fix, AND the theme contains file inclusion functionality that lacks CSRF nonce protection and proper path validation, allowing the CSRF-to-LFI attack chain to be exploited.

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

Update to the latest patched version of Arkhe theme once available, and implement CSRF nonce tokens on all state-changing operations plus validate and sanitize all file inclusion paths to prevent directory traversal.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26748 — 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-26748 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