CVE-2025-8898
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 Taxi Booking Manager for Woocommerce | E-cab plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.3.0. This is due to the plugin not properly validating a user's capabilities prior to updating a plugin setting or their identity prior to updating their details like email address. This makes it possible for unauthenticated attackers to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account. CVE-2025-54713 is likely a duplicate of this issue.
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 Taxi Booking Manager for WooCommerce (E-cab) WordPress plugin up to version 1.3.0 lacks proper capability checks and user identity validation on AJAX endpoints, allowing unauthenticated attackers to modify any user's email address. By changing an administrator's email and leveraging the password reset functionality, attackers can take over administrative accounts and gain full site access.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm plugin installation and versionAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Taxi Booking Manager for WooCommerce' (or 'E-cab'), and note the version number displayed. Alternatively, check the plugin files in wp-content/plugins/ for a version indicator.Affected if The installed version is 1.3.0 or lower, or no version number is displayed (indicating an unpatched older release).
-
Verify AJAX endpoint exposureReview the plugin directory (wp-content/plugins/taxi-booking-manager or similar) for PHP files containing 'wp_ajax_' or 'add_action' calls. Test accessible AJAX endpoints by checking if unauthenticated requests to wp-admin/admin-ajax.php with plugin-related actions return expected responses rather than a 0 or permission denied error.Affected if The plugin handles AJAX requests without verifying user capabilities, allowing unauthenticated access to its callback functions.
-
Inspect user accounts for unauthorized email changesIn WordPress admin, go to Users > All Users. For each administrator account, verify the listed email address matches the original expected address. Check user metadata tables (wp_usermeta) for recent modifications. Compare current emails against any known good baseline or audit logs.Affected if Any administrative user account displays an unfamiliar or suspicious email address that was not set by legitimate administrators.
-
Review access logs for plugin-related requestsExamine web server access logs (Apache, Nginx) for requests to admin-ajax.php containing the plugin's AJAX action names, particularly POST requests from IP addresses not belonging to legitimate administrators. Look for repeated requests modifying user data.Affected if Logs show unauthenticated POST requests targeting the plugin's AJAX endpoints, especially those modifying user email or password reset-related parameters.
You are affected if the Taxi Booking Manager plugin version is 1.3.0 or lower and any administrative user accounts have unauthorized email addresses, or if unauthenticated requests to the plugin's AJAX functionality are possible without validation.
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.
From vendor dataUpdate the Taxi Booking Manager plugin to version 1.3.1 or later immediately. Review user accounts for unauthorized changes and audit administrative users for any created or modified accounts.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8898 — 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-8898 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