dbcve.org
Print Labels With BarcodesWordPress extension · Ukrsolution

CVE-2024-1677

HIGH · 8.8 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 3.4.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The Print Labels with Barcodes. Create price tags, product labels, order labels for WooCommerce plugin for WordPress is vulnerable to unauthorized access of data, modification of data, and loss of data due to an improper capability check on 42 separate AJAX functions in all versions up to, and including, 3.4.6. This makes it possible for authenticated attackers, with subscriber access and above, to fully control the plugin which includes the ability to modify plugin settings and profiles, and create, edit, retrieve, and delete templates and barcodes.

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 confidence

The WooCommerce label and barcode plugin fails to perform capability checks on 42 AJAX endpoints, allowing any authenticated user with subscriber-level access (the lowest WordPress privilege) to modify plugin settings, profiles, and perform full CRUD operations on templates and barcodes. This is a classic Insecure Direct Object Reference (IDOR) combined with broken access control vulnerability.

MitigationUpdate the plugin to version 3.4.7 or later which includes proper capability validation on all AJAX functions. If immediate update is not possible, disable the plugin or restrict AJAX access at the server level until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Print Labels With BarcodesWordPress extension
Affected:< 3.4.7

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the plugin is installed
    Check if the 'Ukrsolution Print Labels With Barcodes' plugin directory exists in your WordPress plugins folder (wp-content/plugins/). You can list installed plugins via WP Admin > Plugins or by examining the filesystem.
    Affected if The plugin is present in the installation
  2. Identify the installed version
    Open the main plugin PHP file (typically in wp-content/plugins/ukrsolution-prilb/) and locate the version declaration in the plugin header comment, or check the readme.txt file for the 'Stable tag' value.
    Affected if The version number found is lower than 3.4.7 (e.g., 3.4.6, 3.4.5, etc.)
  3. Verify WordPress user roles exist
    Log into WordPress admin and navigate to Users > All Users to confirm at least one user with 'Subscriber' role exists, or query the wp_usermeta table for users with wp_capabilities containing 'subscriber'.
    Affected if Any Subscriber-level user account exists in the WordPress installation
  4. Test AJAX endpoint accessibility
    Send a crafted POST request to /wp-admin/admin-ajax.php with a low-privilege subscriber user's authentication cookie and an action parameter corresponding to one of the plugin's AJAX handlers (e.g., action=ukrsolution_update_template). Check if the request succeeds without returning a capability error.
    Affected if The AJAX call returns successful data or modifies content instead of returning a 403/401 error or capability check failure

You are affected if the plugin version is below 3.4.7 and any subscriber-level user account can access the plugin's AJAX endpoints without proper permission checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.4.7 or later
Fixed in 3.4.7
Interim mitigation

Update the plugin to version 3.4.7 or later which includes proper capability validation on all AJAX functions. If immediate update is not possible, disable the plugin or restrict AJAX access at the server level until patched.

Recommended fix High confidence

3.4.7

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find 'Print Labels With Barcodes' in the plugin list
  4. Click 'Update now' if an update to version 3.4.7 is available, or manually upload version 3.4.7
  5. Verify the update was successful by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Print Labels With Barcodes Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1677 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1677 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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