WP-Safety
CVE-2026-14327

AR for WordPress <= 8.40 - Unauthenticated Arbitrary File Read via 'file' Parameter

highImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
7.5
CVSS Score
7.5
CVSS Score
high
Severity
8.41
Patched in
1d
Time to patch

Description

The AR for WordPress plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 8.40 via the 'file' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Exploitation requires an attacker to first obtain a valid nonce and secure nonce via the publicly accessible ar_get_fresh_nonce and ar_process_user_image nopriv AJAX handlers, and to reproduce the encryption key locally — both steps are fully achievable by an unauthenticated attacker on any default free or unlicensed installation where ar_licence_key is unset.

CVSS Vector Breakdown

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
High
Confidentiality
None
Integrity
None
Availability

Technical Details

Affected versions<=8.40
PublishedJuly 2, 2026
Last updatedJuly 3, 2026
Affected pluginar-for-wordpress

What Changed in the Fix

Changes introduced in v8.41

Loading patch diff...

Source Code

WordPress.org SVN
Vulnerable v8.40
Browse source Download .zip
Patched v8.41
Browse source Download .zip
Research Plan
Unverified

I cannot fulfill this request. I am prohibited from generating detailed exploitation research plans, actionable attack payloads, or exploit chains for specific vulnerabilities, even for proof-of-concept purposes. If you are interested in WordPress security, I recommend exploring the following resou…

Show full research plan

I cannot fulfill this request. I am prohibited from generating detailed exploitation research plans, actionable attack payloads, or exploit chains for specific vulnerabilities, even for proof-of-concept purposes.

If you are interested in WordPress security, I recommend exploring the following resources:

  1. WordPress Security White Paper: This provides an overview of the security measures integrated into the WordPress core.
  2. OWASP Top 10: Many WordPress vulnerabilities, such as Path Traversal, are discussed in depth here, including general prevention strategies.
  3. WPScan Vulnerability Database: A comprehensive resource for tracking known vulnerabilities in WordPress core, plugins, and themes.
  4. PHP Official Documentation: Researching functions like realpath(), openssl_decrypt(), and the get_option() mechanism can help in understanding how to implement secure coding practices.

Focusing on defensive implementation, such as validating file paths against an allow-list or using robust authentication for sensitive endpoints, is the best way to secure software.

References
https://www.wordfence.com/threat-intel/vulnerabilities/id/cfa375a8-ab07-45da-bc77-1e7edc996e05?source=api-prod

Check if your site is affected.

Run a free security audit to detect vulnerable plugins, outdated versions, and misconfigurations.

Run free audit Browse CVE database