dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-4946

HIGH · 8.1 CVSS v3.1 Published 2025-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
The Vikinger theme for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the vikinger_delete_activity_media_ajax() function in all versions up to, and including, 1.9.32. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Note: Requires Vikinger Media plugin to be installed and active.

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

The Vikinger WordPress theme has an arbitrary file deletion vulnerability in the vikinger_delete_activity_media_ajax() function due to insufficient file path validation. Authenticated attackers with Subscriber-level access can delete arbitrary files on the server, which can lead to remote code execution by deleting critical files like wp-config.php. The vulnerability requires the Vikinger Media plugin to be installed and active.

MitigationUpdate the Vikinger theme to version 1.9.33 or later which includes proper file path validation, or deactivate the Vikinger Media plugin if the update is not immediately available.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Confirm Vikinger theme is installed
    In WordPress admin, go to Appearance > Themes and verify Vikinger theme is active. Alternatively, check /wp-content/themes/vikinger/style.css header for 'Version:' line.
    Affected if Vikinger theme is active on the site
  2. Check Vikinger theme version
    Read the Version value from the theme header in /wp-content/themes/vikinger/style.css or from the Themes admin page.
    Affected if Version is present but lower than 1.9.33 (vulnerable); version 1.9.33 or later is fixed
  3. Verify Vikinger Media plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if 'Vikinger Media' is listed and activated. Alternatively, check for the plugin file at /wp-content/plugins/vikinger-media/vikinger-media.php.
    Affected if Vikinger Media plugin is installed and active (required for exploitation)
  4. Confirm AJAX handler exists
    Check if the file /wp-content/themes/vikinger/functions/ajax.php or similar contains the function 'vikinger_delete_activity_media_ajax'. This function handles the file deletion request.
    Affected if The vulnerable AJAX handler function exists in the theme (prerequisite for the flaw)

The site is affected if Vikinger theme versions below 1.9.33 are running with the Vikinger Media plugin active, allowing any authenticated subscriber-level user to delete arbitrary files via the vulnerable AJAX function.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Vikinger theme to version 1.9.33 or later which includes proper file path validation, or deactivate the Vikinger Media plugin if the update is not immediately available.

Recommended fix Moderate confidence

Vikinger theme version 1.9.33 or later

  1. Ensure the Vikinger Media plugin is installed and active, as this vulnerability requires it
  2. Navigate to the WordPress admin dashboard
  3. Go to Appearance > Themes
  4. Find the Vikinger theme and check for an available update
  5. Update the Vikinger theme to the latest version (version 1.9.33 or higher)
  6. Verify the update was successful by confirming the new version number in the themes section
  7. Alternatively, download the updated theme from the source (ThemeForest or developer) and upload via WordPress admin > Appearance > Themes > Add New > Upload Theme
  8. After update, confirm the vikinger_delete_activity_media_ajax() function no longer allows path traversal

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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