dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32363

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in Funlus Oy WPLifeCycle free-php-version-info allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPLifeCycle: from n/a through <= 3.3.1.

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 confidence

This is a missing authorization vulnerability in the WPLifeCycle WordPress plugin (free-php-version-info) developed by Funlus Oy. The plugin fails to properly enforce authorization checks on certain functions or endpoints, allowing unauthenticated or lower-privileged users to access functionality that should be restricted to higher-privilege users. This enables attackers to exploit incorrectly configured access control security levels within the plugin.

MitigationImplement proper capability checks and authorization validation on all sensitive functions and AJAX endpoints within the plugin. If a patched version is available, upgrade to the latest version. Otherwise, restrict access to the affected plugin functionality at the web server or WordPress level until proper authorization can be implemented.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WPLifeCycle plugin is installed
    Locate the plugin directory in your WordPress installation at wp-content/plugins/ and check for a folder named 'wplifecycle' or 'wp-life-cycle' or similar. Alternatively, check the WordPress admin plugins list.
    Affected if The WPLifeCycle plugin (free-php-version-info) by Funlus Oy is found installed on the WordPress site
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually in the plugin root folder) and look for the version header comment or a version constant. In WordPress admin, go to Plugins > Installed Plugins and find the version listed for WPLifeCycle.
    Affected if The installed version matches or falls within any affected version range for this vulnerability
  3. Inspect plugin AJAX endpoints for authorization gaps
    Examine the main plugin PHP file for wp_ajax_ and wp_ajax_nopriv_ hooks. Check if functions hooked via wp_ajax_nopriv_ (accessible to unauthenticated users) perform sensitive operations without capability checks using current_user_can() or similar authorization functions.
    Affected if AJAX endpoints registered with wp_ajax_nopriv_ handle sensitive data or actions without verifying user capabilities
  4. Check admin pages for missing capability checks
    Review the plugin code for add_menu_page, add_submenu_page, or admin_menu hook callbacks. Verify that callback functions include current_user_can() checks before executing privileged operations.
    Affected if Admin menu pages or functions can be accessed or executed by users lacking proper WordPress capabilities (like administrator)
  5. Test unauthenticated access to plugin functions
    Use a tool like curl or Burp Suite to send requests to the site's wp-admin/admin-ajax.php endpoint with the plugin's registered AJAX actions, without providing authentication cookies. Check if sensitive data is returned or actions execute.
    Affected if Unauthenticated requests to plugin AJAX actions return sensitive information or perform actions that should require higher privileges

Your environment is affected if the WPLifeCycle plugin by Funlus Oy is installed and its AJAX endpoints or admin functions lack proper capability checks, allowing unauthenticated or low-privileged users to access restricted functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper capability checks and authorization validation on all sensitive functions and AJAX endpoints within the plugin. If a patched version is available, upgrade to the latest version. Otherwise, restrict access to the affected plugin functionality at the web server or WordPress level until proper authorization can be implemented.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32363 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32363 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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