CVE-2025-22318
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 enituretechnology Standard Box Sizes – for WooCommerce standard-box-sizes.This issue affects Standard Box Sizes – for WooCommerce: from n/a through <= 1.6.13.
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 confidenceThis is a missing authorization vulnerability in the enituretechnology Standard Box Sizes WooCommerce plugin. The flaw allows unauthenticated or unauthorized users to potentially access or modify shipping box size configurations without proper capability checks, likely through exposed AJAX endpoints or admin actions lacking authorization validation.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Locate the plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder containing 'standard-box-sizes' or 'eniture' related to box sizes. Identify the main plugin PHP file and read its header for the Version field.Affected if The plugin folder exists and contains the Standard Box Sizes plugin files.
-
Determine the installed versionOpen the main plugin file and locate the 'Version:' header comment, or check the WordPress plugin admin page for the installed version number.Affected if The installed version is 1.6.13 or lower.
-
Inspect AJAX endpoints for authorizationSearch plugin PHP files for 'add_action' calls registering AJAX actions (both 'wp_ajax_' and 'wp_ajax_nopriv_' prefixes). Examine whether these handlers include capability checks (current_user_can, check_admin_referer, wp_verify_nonce) before executing sensitive operations.Affected if AJAX endpoints exist that process box size configurations without capability or nonce validation checks.
-
Verify admin action handlersSearch for 'add_action' calls on admin_init, admin_post, or similar admin hooks that handle box size submissions. Review if these handlers verify user capabilities or nonce tokens before saving configuration changes.Affected if Admin action handlers process box size configuration saves without proper authorization validation.
-
Test unauthenticated access (if safe to do so)If you have a staging environment, attempt to access common plugin AJAX endpoints (check plugin for action names like 'save_box_size', 'update_box', or similar) without providing authentication credentials or nonce tokens.Affected if Requests to box configuration endpoints succeed without authentication.
You are affected if the Standard Box Sizes plugin is installed at version 1.6.13 or lower, or if the plugin lacks capability checks and nonce validation on its AJAX or admin action handlers that manage box size configurations.
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 Standard Box Sizes – for WooCommerce plugin to the latest version beyond 1.6.13, which should contain proper authorization controls. Review and enforce capability checks and nonce validation on all sensitive functions.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22318 — 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-22318 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