dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-13543

HIGH · 8.8 CVSS v3.1 Published 2025-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 PostGallery plugin for WordPress is vulnerable to arbitrary file uploads due to incorrect file type validation in the 'PostGalleryUploader' class functions in all versions up to, and including, 1.12.5. This makes it possible for authenticated attackers, with subscriber-level and above permissions, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 PostGallery WordPress plugin's PostGalleryUploader class fails to properly validate file types during upload, allowing authenticated users with subscriber-level or higher permissions to upload arbitrary files to the server. This insufficient file type validation enables potential remote code execution if attackers upload malicious PHP files.

MitigationUpdate PostGallery plugin to version 1.12.6 or later; if no update is available, disable the plugin immediately and review uploaded files for suspicious content.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Confirm PostGallery plugin is installed
    Navigate to WordPress admin > Plugins and locate PostGallery in the list, or check the /wp-content/plugins/ directory for a postgallery folder
    Affected if PostGallery plugin is present and active in the WordPress installation
  2. Identify the installed PostGallery version
    In WordPress admin > Plugins, click on the PostGallery plugin to view its version number, or inspect the plugin's main PHP file header for the Version tag
    Affected if The installed version is lower than 1.12.6 (the fixed version)
  3. Check for suspicious files in the uploads directory
    Examine the /wp-content/uploads/ directory (and subdirectories by year/month) for unfamiliar .php files, shell scripts, or executable files that were not intentionally uploaded by administrators
    Affected if Unexpected PHP files or other executable content exists in upload folders
  4. Verify subscriber-level users exist
    In WordPress admin > Users, review the user list to determine if any users with Subscriber role (or higher-privilege roles) are present on the site
    Affected if At least one user with Subscriber role or higher exists in the system
  5. Confirm upload functionality is accessible
    Check if the PostGallery uploader endpoint exists and is reachable; inspect plugin code for the PostGalleryUploader class and verify the upload form or AJAX handler is active
    Affected if The upload functionality is enabled and the uploader endpoint responds to requests

You are affected if PostGallery plugin is installed with a version lower than 1.12.6, subscriber-level or higher users exist, and the upload functionality is accessible without proper file type restrictions.

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 PostGallery plugin to version 1.12.6 or later; if no update is available, disable the plugin immediately and review uploaded files for suspicious content.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (newer than 1.12.5)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the PostGallery plugin
  4. Check if an update is available and install the latest version
  5. If no update is available through WordPress, manually download the latest version from the official WordPress plugin repository at plugins.trac.wordpress.org/plugin/post-gallery
  6. Deactivate the old version, delete it, then upload and activate the new version

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

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-2025-13543 — 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-13543 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