CVE-2025-60247
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 · uneditedMissing Authorization vulnerability in Bux Bux Woocommerce bux-woocommerce allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Bux Woocommerce: from n/a through <= 1.2.3.
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 · moderate confidenceThe bux-woocommerce WordPress plugin (versions up to 1.2.3) contains a missing authorization vulnerability where certain functionality is not properly constrained by access control lists. This allows authenticated users to access administrative or privileged functions they should not have permission to 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 if bux-woocommerce plugin is installedLog in to WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'bux-woocommerce'Affected if The plugin is present in the WordPress installation
-
Check the installed plugin versionIn WordPress admin, find bux-woocommerce in the plugins list and view the version number in the plugin description, or read the 'Version' field in the plugin's main PHP file headerAffected if The version is 1.2.3 or lower (any version up to and including 1.2.3)
-
Confirm the plugin is activeIn WordPress admin > Plugins, verify that bux-woocommerce shows as 'Active' under the plugin statusAffected if The plugin is activated and running on the site
-
Review user accounts and rolesIn WordPress admin > Users, list all registered users and examine their assigned roles (Administrator, Editor, Author, Subscriber, etc.)Affected if There are multiple user accounts, particularly any with Administrator or Editor roles that were not created by a known site administrator
-
Check for unauthorized access to admin functionsReview WordPress activity logs, server access logs, or security plugins for any actions performed by lower-privileged users that modified plugin settings, user accounts, or site content outside their normal permissionsAffected if Logs show actions performed by non-administrator users that access plugin administrative functions or privileged WordPress features
Your environment is affected if the bux-woocommerce plugin is installed, active, and running version 1.2.3 or lower.
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 bux-woocommerce plugin to a patched version once available. Until then, restrict user access to only trusted, authorized personnel and monitor for suspicious administrative actions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60247 — 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-60247 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