CVE-2026-32377
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 Pranayama Yoga pranayama-yoga allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Pranayama Yoga: from n/a through <= 1.2.2.
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 confidenceA missing authorization vulnerability in the Pranayama Yoga WordPress theme allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to protected functionality due to absent or inadequate permission checks.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Pranayama Yoga theme is installedNavigate to Appearance > Themes in WordPress admin, or check /wp-content/themes/ directory for pranayama-yoga or similar theme folderAffected if The Pranayama Yoga theme is active or installed on the WordPress site
-
Identify installed theme versionCheck theme style.css header for Version field, or view theme functions.php for version constantAffected if Unable to determine version or version is unknown/unpatched
-
Inspect theme for admin-level functionalitySearch theme files (functions.php, admin.php, or any *_admin*.php files) for actions like add_menu_page, add_submenu_page, or AJAX handlers that perform sensitive operationsAffected if Theme contains admin functionality accessible without capability checks (like manage_options or upload_files)
-
Check for missing capability checksSearch theme PHP files for do_action or add_action hooks that modify content/settings and verify if they include current_user_can() or similar authorization checks before executingAffected if Theme functions that modify settings, content, or perform admin-level actions lack current_user_can() validation
-
Test publicly accessible sensitive functionsAccess theme AJAX endpoints (admin-ajax.php?action=theme_action) or direct PHP files in theme directory without authentication to see if protected functions executeAffected if Sensitive operations execute without requiring login or verifying user permissions
A site is affected if it has the Pranayama Yoga theme installed and any unprotected admin-level functions or AJAX handlers exist without proper current_user_can() authorization checks.
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 dataImplement proper authorization checks and role-based access controls throughout the theme to verify user permissions before executing sensitive operations.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32377 — 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-32377 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