CVE-2026-32370
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 Influencer influencer allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Influencer: from n/a through <= 1.1.7.
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 Influencer WordPress theme allows unauthenticated or unauthorized users to access functionality that should be protected by access controls. The theme has incorrectly configured security levels that fail to properly validate user permissions before granting access to sensitive features.
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.
-
Locate the installed theme versionCheck the style.css file in wp-content/themes/raratheme-influencer/ for the 'Version:' comment in the file header, or query the WordPress database in wp_options where option_name contains 'theme_mods_raratheme-influencer'Affected if The version cannot be determined or is an unpatched release
-
Identify sensitive PHP callback functionsSearch theme PHP files (functions.php, any files in /inc/ or /admin/ folders) for function definitions that handle form submissions, data updates, or settings changes. Look for add_action hooks with 'admin_init', 'init', or 'wp_ajax_' prefixesAffected if Functions that modify data or access sensitive features lack current_user_can() capability checks
-
Verify authorization on AJAX endpointsSearch for wp_ajax_ and wp_ajax_nopriv_ action hooks in the theme. For each handler, examine whether it calls current_user_can() or a permission check before executing sensitive operationsAffected if AJAX handlers registered with wp_ajax_nopriv_ or handlers without capability verification allow unauthenticated access
-
Inspect admin page handlersReview add_action calls with 'admin_post_' or 'admin_init' hooks. Check if admin pages (under /admin/ folder or in functions.php) validate user capabilities before processing requestsAffected if Admin action handlers do not verify user permissions via current_user_can() or similar checks
-
Check for missing nonce validationSearch theme PHP files for wp_nonce_field, wp_verify_nonce, or check_admin_referer calls around sensitive operations (form handlers, settings updates, data modifications)Affected if Forms or request handlers lack nonce verification, allowing CSRF attacks in conjunction with missing authorization
A user is affected if the theme allows unauthenticated or unauthorized access to sensitive functionality due to missing capability checks (current_user_can()) or nonce verification in callback functions, AJAX handlers, or admin action hooks.
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 dataApply proper authorization checks (capability checks, nonce verification, and access control validation) to all sensitive functions and admin actions within the theme. Update to the latest patched version when available.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32370 — 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-32370 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