CVE-2025-12350
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 · uneditedThe DominoKit plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the wp_ajax_nopriv_dominokit_option_admin_action AJAX endpoint in all versions up to, and including, 1.1.0. This makes it possible for unauthenticated attackers to update plugin settings.
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 confidenceThe DominoKit WordPress plugin has a broken access control vulnerability where the AJAX endpoint wp_ajax_nopriv_dominokit_option_admin_action lacks proper capability verification. The 'nopriv' prefix makes this endpoint accessible to unauthenticated users, allowing them to modify plugin settings without any privileges.
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.
-
Verify DominoKit plugin is installedCheck the WordPress plugins directory or use wp-cli: wp plugin list --status=active --format=csv | grep -i dominokitAffected if DominoKit plugin is active on the WordPress installation
-
Check the installed DominoKit versionInspect the plugin header in dominokit.php or use wp-cli: wp plugin get dominokit --field=versionAffected if Version is lower than 1.1.1 or version cannot be determined (plugin may be outdated)
-
Verify the vulnerable AJAX endpoint existsCheck if the file containing wp_ajax_nopriv_dominokit_option_admin_action exists in the plugin directory; search the plugin PHP files for the string 'wp_ajax_nopriv_dominokit_option_admin_action'Affected if The AJAX handler with 'nopriv' prefix is present in the plugin code
-
Confirm lack of capability check in the AJAX handlerSearch the plugin PHP files for the function handling dominokit_option_admin_action and verify it does not contain current_user_can() or a capability check before processing the requestAffected if The AJAX handler allows execution without verifying user capabilities (no current_user_can() call present)
A user is affected if the DominoKit plugin is installed with a version below 1.1.1 and the vulnerable AJAX endpoint wp_ajax_nopriv_dominokit_option_admin_action is accessible without capability verification.
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.
dbcve · scopedUpdate the DominoKit plugin to version 1.1.1 or later if available, or disable the plugin until a patch can be applied. If no patch exists, manually add a capability check (e.g., current_user_can('manage_options')) to the AJAX handler.
Update to the latest version of DominoKit (version higher than 1.1.0)
- Go to WordPress admin dashboard > Plugins > Installed Plugins
- Locate the DominoKit plugin
- Check if an update is available for DominoKit
- If an update is available, click 'Update Now' to install the latest version
- After updating, verify the plugin settings have not been altered by navigating to the DominoKit settings page
- Confirm that unauthorized changes have not been persisted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12350 — 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-2025-12350 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