dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-2375

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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
The App Builder – Create Native Android & iOS Apps On The Flight plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 5.5.10. This is due to the `verify_role()` function in `AuthTrails.php` explicitly whitelisting the `wcfm_vendor` role alongside `subscriber` and `customer`, and assigning it directly via `wp_insert_user()` without integrating with WCFM Marketplace's vendor approval workflow. This makes it possible for unauthenticated attackers to register an account with the `wcfm_vendor` role by supplying the `role` parameter in the `/wp-json/app-builder/v1/register` REST API endpoint, bypassing the standard WCFM vendor approval process and immediately gaining vendor-level privileges (product management, order access, store management) on sites where WCFM Marketplace is active.

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 · high confidence

The App Builder WordPress plugin allows unauthenticated users to register with the privileged 'wcfm_vendor' role via the /wp-json/app-builder/v1/register REST API endpoint. The verify_role() function in AuthTrails.php explicitly whitelists wcfm_vendor alongside subscriber and customer, then assigns it directly through wp_insert_user() without invoking WCFM Marketplace's vendor approval workflow, granting immediate vendor-level access to product, order, and store management.

MitigationUpdate to a patched version of the plugin once available, or temporarily disable the app-builder REST API registration endpoint and audit recent user registrations for unauthorized vendor accounts.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 App Builder plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'App Builder' or check the plugin files in /wp-content/plugins/ directory for the app-builder folder. Check the plugin version in the plugin header.
    Affected if The App Builder plugin is installed and the version is within the affected range (unpatched versions)
  2. Confirm REST API endpoint exposure
    Make a GET request to /wp-json/app-builder/v1/register using curl or a browser. A 200 OK response indicates the endpoint exists and is accessible.
    Affected if The endpoint returns a successful response, indicating the vulnerable API is exposed
  3. Check for wcfm_vendor role presence
    In WordPress admin, go to Users > Users and look for users with 'wcfm_vendor' role, or query the wp_usermeta table for meta_key = 'wp_capabilities' containing 'wcfm_vendor'.
    Affected if Any user accounts exist with the wcfm_vendor role
  4. Audit recent user registrations
    Review user registration dates in wp_users table and role assignments in wp_usermeta. Compare against expected vendor onboarding through WCFM Marketplace's normal approval workflow.
    Affected if Users with wcfm_vendor role were created without going through the WCFM Marketplace vendor approval process, especially around the time the App Builder plugin was active

If the App Builder plugin is installed with the vulnerable REST API endpoint exposed and any wcfm_vendor role accounts exist that bypassed the normal WCFM Marketplace approval workflow, the environment is affected by CVE-2026-2375.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the plugin once available, or temporarily disable the app-builder REST API registration endpoint and audit recent user registrations for unauthorized vendor accounts.

Recommended fix Moderate confidence

Latest version beyond 5.5.10 from wordpress.org/plugins/app-builder/

  1. Check the current version of the App Builder – Create Native Android & iOS Apps On The Flight plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the plugin version is 5.5.10 or lower, update to the latest available version via the WordPress plugin repository
  4. After updating, verify the `/wp-json/app-builder/v1/register` endpoint no longer accepts arbitrary role parameters
  5. Confirm that new user registration via the app builder endpoint properly respects WCFM Marketplace's vendor approval workflow
Caveat Review plugin changelog for any breaking changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2375 — 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-2375 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