dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-11367

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 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 PixMagix – WordPress Image Editor plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.7.2 via the move_image_on_server function. This makes it possible for authenticated attackers, with author-level access and above, to write files with attacker-controlled content to arbitrary locations on the server. The unsanitized 'layers[].id' parameter is concatenated into a filesystem path and passed to PHP's copy() function, allowing traversal sequences (e.g. '../../') to escape the intended upload directory and write attacker-supplied file contents to arbitrary paths accessible by the web server process. The save_template REST endpoint is gated by the create_projects permission (edit_pixmagix + upload_files), which Author-level users hold by default after plugin activation, making this exploitable by any Author on sites running PixMagix.

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 PixMagix WordPress plugin has a directory traversal vulnerability in the move_image_on_server function. The unsanitized 'layers[].id' parameter is directly concatenated into a filesystem path and passed to PHP's copy() function, allowing authenticated users with Author-level access to use traversal sequences (e.g. '../../') to escape the intended upload directory and write attacker-controlled file contents to arbitrary locations accessible by the web server process.

MitigationUpgrade to version 1.7.3 or later which should contain proper path sanitization. Until then, restrict the edit_pixmagix and upload_files capabilities to only trusted Administrator-level users, or deactivate the plugin.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Confirm PixMagix plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a pixmagix folder, or query the wp_plugins table for an active plugin with 'pixmagix' in the plugin slug.
    Affected if The pixmagix folder exists in plugins and the plugin is active in WordPress.
  2. Identify the installed PixMagix version
    Open the main plugin file (e.g., pixmagix.php) in the plugin folder and locate the version comment or Version: header in the file docblock. Compare this version number to 1.7.3.
    Affected if The installed version is lower than 1.7.3 or the version cannot be determined (version header missing).
  3. Verify user role capabilities
    Query the WordPress database: SELECT u.user_login, u.user_email, m.meta_value FROM wp_users u JOIN wp_usermeta m ON u.ID = m.user_id WHERE m.meta_key = 'wp_capabilities'. Check if any non-Administrator users have roles containing 'author', 'editor', or 'contributor', or have explicit 'edit_pixmagix' or 'upload_files' capabilities assigned.
    Affected if Any user with Author-level access or higher (or explicit edit_pixmagix/upload_files capability) exists besides trusted Administrator accounts.
  4. Confirm the vulnerable function exists
    Examine the plugin source code for the move_image_on_server function. Search for 'function move_image_on_server' and verify it accepts a 'layers' array parameter. Check if the function directly uses $_POST['layers'] without sanitization.
    Affected if The move_image_on_server function exists and processes the layers[].id parameter without sanitization before passing it to PHP's copy() function.

The environment is affected if the PixMagix plugin is active, installed version is below 1.7.3, and any user with Author-level or higher access (or explicit edit_pixmagix/upload_files capability) exists in WordPress.

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

Upgrade to version 1.7.3 or later which should contain proper path sanitization. Until then, restrict the edit_pixmagix and upload_files capabilities to only trusted Administrator-level users, or deactivate the plugin.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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