CVE-2026-10830
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 AllCoach WordPress plugin before 1.0.2 does not verify that an email address submitted to a public account-registration endpoint is not already associated with an existing user before overwriting that user's password, allowing unauthenticated attackers to reset the password of arbitrary accounts, including administrators, and take over the site.
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 AllCoach WordPress plugin before 1.0.2 has a critical authentication bypass in its public account-registration endpoint. The plugin fails to validate whether a submitted email address already exists in the WordPress user database before processing password reset requests, allowing unauthenticated attackers to overwrite passwords of any existing user including administrators.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 AllCoach plugin is installedLog in to WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for an allcoach folderAffected if The AllCoach plugin folder exists in the WordPress plugins directory
-
Check installed AllCoach versionIn WordPress admin, find AllCoach in the plugins list and view the version number displayed, or read the main plugin PHP file header for the 'Version' tagAffected if Version number is below 1.0.2 or no version is displayed (indicating an unpatched release)
-
Confirm plugin is activeIn WordPress admin > Plugins, verify the AllCoach plugin shows as 'Active'Affected if Plugin is active and the vulnerable password reset/registration endpoint is publicly accessible
Your environment is affected if the AllCoach WordPress plugin is installed, active, and running a version earlier than 1.0.2, allowing unauthenticated access to the password reset endpoint.
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 · scopedUpgrade AllCoach plugin to version 1.0.2 or later which implements proper email existence validation before allowing password changes. As an interim measure, disable the plugin until patched.
AllCoach plugin version 1.0.2
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the AllCoach plugin
- If an update to version 1.0.2 or later is available, click 'Update Now'
- Verify the plugin is running version 1.0.2 or later after updating
- As a precaution, review and change passwords for administrator-level user accounts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10830 — 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-10830 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