CVE-2026-32345
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 · uneditedMissing Authorization vulnerability in raratheme Perfect Portfolio perfect-portfolio allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Perfect Portfolio: from n/a through <= 1.2.4.
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 confidenceMissing Authorization vulnerability in the raratheme Perfect Portfolio WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The vulnerability exists in versions up to and including 1.2.4, potentially allowing unauthorized access to sensitive functionality or data due to missing capability checks or improper access control configuration.
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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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.
-
Check if Perfect Portfolio plugin is installedLook for the plugin directory at wp-content/plugins/perfect-portfolio/ or check in WordPress admin under Plugins > Installed Plugins for 'Perfect Portfolio' by rarathemeAffected if Plugin is not found means not affected; if found, continue to version check
-
Verify the installed version numberOpen the main plugin file (usually perfect-portfolio.php) in the plugin directory and look for the 'Version:' comment in the file header, or check the Plugins page in WordPress adminAffected if Version is 1.2.4 or lower indicates potentially affected; versions above 1.2.4 are not affected
-
Inspect plugin for missing capability checks in AJAX handlersSearch the plugin PHP files for wp_ajax_ hooks and verify each handler includes a current_user_can() check before processing the requestAffected if Any AJAX handler lacks a current_user_can() capability check before executing sensitive operations
-
Inspect admin page rendering for missing capability checksReview admin PHP files for page rendering functions and verify they include current_user_can() checks before displaying or processing sensitive dataAffected if Any admin page or function renders sensitive information without verifying user capabilities
The environment is affected if Perfect Portfolio plugin version 1.2.4 or lower is installed AND the plugin code lacks proper current_user_can() capability checks on sensitive AJAX handlers or admin page functions.
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 to the latest version of Perfect Portfolio when a patch is released. If no update is available, audit the plugin's admin functions and add proper capability checks (current_user_can) and nonce verification to all sensitive AJAX handlers and page renders.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32345 — 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-32345 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