CVE-2025-13376
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 · uneditedThe ProjectList plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all versions up to, and including, 0.3.0. This makes it possible for authenticated attackers, with Editor-level access and above, 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 confidenceThe ProjectList WordPress plugin lacks proper file type validation in its upload functionality, enabling authenticated users with Editor-level access or higher to upload arbitrary files to the server, which can lead to 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify ProjectList plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'ProjectList' in the list. Note whether it is active or inactive.Affected if The plugin is installed and active, making the vulnerable code accessible.
-
Identify installed ProjectList versionIn the Plugins list, click on the ProjectList plugin to view its details, or inspect the plugin header in /wp-content/plugins/projectlist/plugin.php to find the 'Version' field.Affected if The version is 0.3.0 or lower, which lacks proper file type validation.
-
Confirm Editor or higher roles existNavigate to Users > All Users in WordPress admin and review the role assigned to each user. Check if any users have Editor, Author, or Administrator roles.Affected if At least one user with Editor-level or higher access exists, enabling authenticated exploitation.
-
Verify upload functionality is accessibleAttempt to access the ProjectList plugin settings or upload feature. Check if the plugin exposes any file upload endpoints by reviewing the plugin source code in /wp-content/plugins/projectlist/ for file upload forms or handlers.Affected if The upload functionality is present and accessible to authenticated users, allowing the vulnerability to be exploited.
You are affected if the ProjectList plugin is active, version 0.3.0 or lower, and any user with Editor-level or higher access can access the upload functionality.
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 dataUpgrade the ProjectList plugin to a version beyond 0.3.0 where file type validation has been implemented, or disable the plugin until a patch is available.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-13376 — 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-2025-13376 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