CVE-2026-32379
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 Rara Academic rara-academic allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Rara Academic: 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 exists in the Rara Academic WordPress theme (versions <=1.2.2) that allows unauthenticated attackers to access functionality or data due to incorrectly configured access control security levels, as indicated by the CVSS metrics showing no privileges required.
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.
-
Check the installed Rara Academic theme versionNavigate to Appearance > Themes in WordPress admin and view the Rara Academic theme details, or open the file /wp-content/themes/rara-academic/style.css and look for the 'Version:' header in the theme comment blockAffected if The version listed is 1.2.2 or lower
-
Verify the theme is active on the siteIn WordPress admin, go to Appearance > Themes and confirm Rara Academic is the currently active themeAffected if Rara Academic is the active theme in use
-
Inspect theme AJAX actions for missing capability checksExamine the theme's functions.php file for add_action('wp_ajax_*') or add_action('wp_ajax_nopriv_*') calls. Check if any of these actions call current_user_check() or a capability check function like current_user_can() before executing sensitive operationsAffected if AJAX actions exist without current_user_can() or similar authorization checks before processing requests
-
Review theme endpoint access controlsSearch the theme directory for PHP files containing function hooks that handle user data or site functionality (such as form handlers, data export functions, or settings save routines). Verify if these functions include capability checks using current_user_can() or nonce validation using wp_verify_nonce()Affected if Any theme functionality handles requests without verifying user permissions or validating nonces
If the Rara Academic theme version is 1.2.2 or lower and the theme is active, the site is likely affected by this unauthenticated authorization bypass vulnerability.
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 patched version of Rara Academic when available, or audit all theme endpoints and AJAX actions to implement proper capability checks and nonce validation.
- 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-32379 — 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-32379 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