dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3651

MEDIUM · 5.3 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 →
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
The Build App Online plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.0.23. This is due to the plugin registering the 'build-app-online-update-vendor-product' AJAX action via wp_ajax_nopriv_ without proper authentication checks, capability verification, or nonce validation in the update_vendor_product() function. The function accepts a user-supplied post ID from the request and calls wp_update_post() to modify the post_author field without validating whether the user has permission to modify the specified post. This makes it possible for unauthenticated attackers to modify the post_author of arbitrary posts to 0 (orphaning posts from their legitimate authors), or for authenticated attackers to claim ownership of any post by setting themselves as the author.

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 Build App Online WordPress plugin registers the 'build-app-online-update-vendor-product' AJAX action with wp_ajax_nopriv_, making it accessible to unauthenticated users. The update_vendor_product() function accepts a user-supplied post ID and calls wp_update_post() to modify the post_author field without any authentication checks, capability verification, or nonce validation, allowing unauthenticated attackers to orphan posts by setting post_author to 0, or authenticated users to claim ownership of arbitrary posts.

MitigationUpgrade to version 1.0.24 or later which implements proper authentication, capability checks, and nonce validation on the affected AJAX action. Until patched, disable the plugin or restrict access to the vulnerable endpoint.

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. Identify if the Build App Online plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Build App Online', or inspect the /wp-content/plugins/ directory for a folder named 'build-app-online' or similar
    Affected if The plugin appears in the list of installed plugins
  2. Determine the installed plugin version
    In WordPress admin plugins list, click on the plugin to view its details and note the version number, or read the main plugin PHP file header for the 'Version' tag
    Affected if The version is lower than 1.0.24 (the patched version)
  3. Check if any posts can be targeted
    Make a simple POST request to the AJAX endpoint with a post_id parameter (e.g., using curl: curl -X POST http://your-site/wp-admin/admin-ajax.php -d 'action=build-app-online-update-vendor_product&post_id=1&post_author=999')
    Affected if The post's author is successfully changed to the specified value without authentication error

You are affected if the Build App Online plugin is installed with a version before 1.0.24 AND the vulnerable AJAX endpoint responds without authentication.

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

Upgrade to version 1.0.24 or later which implements proper authentication, capability checks, and nonce validation on the affected AJAX action. Until patched, disable the plugin or restrict access to the vulnerable endpoint.

Recommended fix Moderate confidence

Version 1.0.24 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Build App Online' plugin
  4. Click 'Update Now' if an update is available, or manually download the latest version from WordPress.org plugins repository
  5. Verify the update completes successfully
  6. Test that the 'build-app-online-update-vendor-product' AJAX action now requires proper authentication

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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