dbcve.org
CWE-36Weakness · CWE-36

CVE-2026-15302

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 ARMember plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.0.27 via the 'X-FILENAME' HTTP header. This makes it possible for unauthenticated attackers to upload and overwrite certain files (e.g., CSS) to directories outside the 'wp-content/uploads/armember' directory.

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 ARMember WordPress plugin contains a directory traversal vulnerability in its file upload functionality. Attackers can manipulate the X-FILENAME HTTP header to specify arbitrary file paths, allowing upload of files (specifically CSS and similar assets) outside the intended wp-content/uploads/armember directory. This affects all versions up to and including 4.0.27 and can lead to website defacement or overwrite of existing files.

MitigationUpdate the ARMember plugin to a version beyond 4.0.27 when available. If no patched version exists, disable the plugin or implement WAF rules to block manipulation of the X-FILENAME header until a fix is released.

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

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

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 ARMember plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/armember directory on the server
    Affected if ARMember plugin is present on the WordPress site
  2. Determine installed ARMember version
    Check the plugin header in /wp-content/plugins/armember/armember.php for the 'Version:' field, or view it in the WordPress Plugins admin page
    Affected if Version is 4.0.27 or any earlier version (the vulnerability affects all versions up to and including 4.0.27)
  3. Confirm upload functionality is accessible
    Locate the file upload endpoint in the ARMember plugin (typically handles CSS/style imports). Check if the /wp-content/uploads/armember/ directory exists and is writable
    Affected if The plugin's upload feature is enabled and the armember upload directory is present and writable
  4. Inspect HTTP logs for X-FILENAME header manipulation
    Review web server access logs (Apache/nginx) for requests to ARMember upload handlers containing the X-FILENAME header with path traversal patterns (e.g., ../../../)
    Affected if Suspicious requests with manipulated X-FILENAME headers targeting non-armember directories are found in logs

You are affected if ARMember plugin versions 4.0.27 or below are installed AND the file upload functionality is accessible, regardless of whether exploitation attempts are observed in logs

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 ARMember plugin to a version beyond 4.0.27 when available. If no patched version exists, disable the plugin or implement WAF rules to block manipulation of the X-FILENAME header until a fix is released.

Recommended fix Moderate confidence

ARMember version 4.0.28 or later

  1. 1. Navigate to the WordPress admin dashboard for the site using the ARMember plugin
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate ARMember in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest patched version
  5. 5. Alternatively, download the latest version of ARMember from the official WordPress plugin repository (plugins.trac.wordpress.org) and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running on version 4.0.28 or later
  7. 7. Test that the X-FILENAME header no longer allows directory traversal outside the intended uploads directory

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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