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

CVE-2025-60156

CRITICAL · 9.6 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 webandprint AR For WordPress ar-for-wordpress allows Upload a Web Shell to a Web Server.This issue affects AR For WordPress: from n/a through <= 8.34.

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 WordPress plugin 'AR For Wordpress' enables attackers to trick authenticated administrators into unknowingly uploading a web shell to the server. By crafting a malicious request that the victim's browser sends to the vulnerable WordPress site, an attacker can achieve remote code execution through the uploaded shell.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all state-changing admin actions, particularly file upload functionality, and verify these nonces server-side before processing any file uploads. Additionally, add SameSite cookie attributes and implement proper referrer validation.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Verify AR For Wordpress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'AR For Wordpress' or check the plugins directory at /wp-content/plugins/ for a folder starting with 'ar-'. Note the installed version from the plugin headers.
    Affected if The plugin is present in the WordPress installation
  2. Identify file upload endpoint
    Examine the plugin's admin PHP files for form actions handling file uploads, typically look for 'enctype="multipart/form-data"' in forms and corresponding handler files that process $_FILES superglobal.
    Affected if The plugin contains file upload forms in its admin interface without explicit nonce verification in the handler code
  3. Check for nonce verification in upload handler
    Search the plugin's PHP files that process uploads for 'wp_verify_nonce' or 'check_admin_referer' calls immediately before any $_FILES processing. Also check for 'nonce_field' or 'wp_nonce_field' in any upload forms.
    Affected if No nonce verification is performed before processing uploaded files, or nonce checks are missing from the upload form
  4. Inspect cookie configuration for SameSite attribute
    Check WordPress configuration (wp-config.php) and any relevant plugin files for 'setcookie' calls with 'SameSite' attribute, or inspect browser cookies for the WordPress session to verify SameSite=Strict or SameSite=Lax is set.
    Affected if SameSite cookie attribute is not set on WordPress session cookies, making CSRF attacks possible across sites
  5. Verify referrer validation
    Search plugin code for 'wp_referer_field', 'check_admin_referer', or manual $_SERVER['HTTP_REFERER'] validation before processing any state-changing requests including uploads.
    Affected if No referrer validation is performed on file upload requests

A user is affected if the AR For Wordpress plugin is installed and its file upload functionality lacks proper nonce verification and CSRF protections.

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

Implement WordPress nonces (anti-CSRF tokens) on all state-changing admin actions, particularly file upload functionality, and verify these nonces server-side before processing any file uploads. Additionally, add SameSite cookie attributes and implement proper referrer validation.

Recommended fix Moderate confidence

Latest version of AR For WordPress plugin (version > 8.34)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'AR For WordPress' (webandprint AR For WordPress) plugin
  4. 4. Check the current installed version (should be <= 8.34)
  5. 5. Click 'Update Now' if an update is available, or manually download the latest version from the WordPress Plugin Repository
  6. 6. Verify the update was successful and the plugin is now running a version higher than 8.34

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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