CVE-2026-32524
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Jordy Meow Photo Engine wplr-sync allows Upload a Web Shell to a Web Server.This issue affects Photo Engine: from n/a through <= 6.4.9.
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 · moderate confidenceUnrestricted file upload vulnerability in Jordy Meow Photo Engine wplr-sync allows unauthenticated or authenticated attackers to upload web shells to the web server, potentially enabling complete system compromise via remote code execution.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Jordy Meow Photo Engine installationSearch for the Photo Engine plugin or theme files in your WordPress installation (typically in wp-content/plugins/ or wp-content/themes/). Look for directories named 'photo-engine', 'meow-photo', or similar Jordy Meow products.Affected if The plugin or theme is found in the WordPress plugins or themes directory.
-
Verify wplr-sync functionality is presentLocate the wplr-sync component within the Photo Engine installation. Search for files, modules, or endpoints containing 'wplr-sync' in the codebase or exposed URLs.Affected if The wplr-sync functionality exists and is accessible within the installation.
-
Check installed Photo Engine versionIf a version number is displayed in the WordPress admin plugin/theme page, or defined in the main plugin/theme file header, compare it against the patched version provided in the CVE reference.Affected if The installed version matches or falls within the affected version range.
-
Inspect upload directory configurationExamine the web server configuration and the wplr-sync upload handling code to determine where uploaded files are stored. Check if the upload directory is within the web root (public_html, www, htdocs).Affected if Uploaded files are stored in a directory accessible via HTTP/HTTPS.
-
Review file type validationExamine the wplr-sync upload handler to determine if server-side file type validation exists. Look for allowlist logic that restricts uploads to safe file types (images, documents) and rejects executable extensions (.php, .phtml, .exe, .js).Affected if No server-side file type validation exists, or the validation can be easily bypassed.
Your environment is affected if Jordy Meow Photo Engine with wplr-sync is installed, the wplr-sync component is accessible, and uploaded files can be stored in a web-accessible location without proper validation.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Photo Engine to a patched version. Until then, disable wplr-sync functionality, implement strict server-side file type validation (allowlist approach), and store all uploads outside the web root with executable permissions removed.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32524 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32524 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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