Print Labels With BarcodesWordPress extension · Ukrsolution
CVE-2024-1679
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 Print Labels with Barcodes. Create price tags, product labels, order labels for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the template and javascript label fields in all versions up to, and including, 3.4.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 Print Labels with Barcodes plugin for WordPress fails to sanitize and escape input in template and javascript label fields, allowing authenticated users with subscriber-level access to inject persistent malicious scripts that execute when other users access affected pages.
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
< 3.4.7CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Verify plugin installationIn WordPress admin, go to Plugins > Installed Plugins and search for 'Ukrsolution Print Labels With Barcodes' or 'Print Labels With Barcodes'Affected if The plugin is not installed or not found
-
Check installed versionIn WordPress admin, go to Plugins > Installed Plugins, find the Print Labels With Barcodes plugin, and note the version number displayedAffected if Version is less than 3.4.7 (or version number cannot be determined or is not displayed)
-
Confirm subscriber role accessNavigate to Users > Users in WordPress admin, identify users with the Subscriber role, then go to the plugin settings to determine if subscribers can access label template functionalityAffected if Subscriber role users have access to create or edit label templates
-
Inspect label templates for unsanitized inputAccess the plugin label template editor (usually under the plugin menu in WordPress admin), examine template and javascript label fields for any existing injected scripts or unsanitized HTML/script contentAffected if Any label templates contain unsanitized user-supplied content or suspicious script tags
User is affected if the Print Labels With Barcodes plugin version is below 3.4.7 AND subscriber-level users have access to label template functionality.
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 · scoped3.4.7
Update to version 3.4.7 or later which contains the patch. Until then, consider restricting subscriber role capabilities or temporarily disabling the affected label template functionality.
3.4.7
- Backup your WordPress site before making any changes
- Update the Print Labels With Barcodes plugin to version 3.4.7 or later
- Verify the plugin update was successful in the WordPress admin dashboard
- Test the plugin's label generation functionality to ensure it works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Print Labels With Barcodes
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1679 — 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-2024-1679 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