CVE-2026-6962
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 Cost of Goods: Product Cost & Profit Calculator for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'alg_wc_cog_product_cost' and 'alg_wc_cog_product_profit' shortcodes in all versions up to, and including, 4.1.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level 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 · moderate confidenceThe Cost of Goods plugin for WooCommerce contains a stored XSS vulnerability in its 'alg_wc_cog_product_cost' and 'alg_wc_cog_product_profit' shortcodes. Authenticated attackers with contributor-level access can inject malicious scripts through unsanitized shortcode attributes, which execute when users view affected pages.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Identify plugin installation and versionCheck the installed WooCommerce Cost of Goods plugin version in WordPress under Plugins > Installed Plugins, or inspect the plugin header in /wp-content/plugins/cost-of-goods-for-woocommerce/alg-wc-cog.phpAffected if The plugin is installed and version is lower than 4.1.1 (or version cannot be determined)
-
Detect vulnerable shortcode usageSearch WordPress content (posts, pages, widgets, custom post types) for the presence of [alg_wc_cog_product_cost] or [alg_wc_cog_product_profit] shortcode strings using WP admin search, database query, or grep across wp_posts tableAffected if Either shortcode is present in any published content on the site
-
Check for unsanitized shortcode attributesInspect pages containing the shortcodes and view the page source or use browser dev tools to examine how the shortcode attributes are rendered; look for evidence of raw attribute values appearing in HTML output without proper escapingAffected if Shortcode attributes are reflected in output without HTML encoding (visible unsanitized values in page source)
-
Review user role permissionsNavigate to WordPress Users panel and identify accounts with Contributor, Author, Editor, or Administrator roles who have permission to create or edit content containing shortcodesAffected if Any user account with Contributor-level or higher access exists on the site (these roles can exploit the vulnerability)
-
Verify shortcode is publicly accessibleVisit a page or post containing one of the vulnerable shortcodes as a logged-out visitor to confirm the shortcode renders and executes for public usersAffected if The shortcode output is visible to unauthenticated visitors, allowing XSS to execute when they view affected pages
The site is affected if the Cost of Goods plugin version is below 4.1.1 AND the alg_wc_cog_product_cost or alg_wc_cog_product_profit shortcode is in use on any published content, since contributor-level users can inject XSS through unsanitized attributes that execute for all visitors.
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 · scopedUpdate the plugin to version 4.1.1 or later once available. Until then, restrict shortcode usage to trusted users only and consider disabling the affected shortcodes.
Latest version of Cost of Goods: Product Cost & Profit Calculator for WooCommerce plugin (version > 4.1.0)
- 1. Log in to the WordPress admin dashboard with an account that has administrator privileges.
- 2. Navigate to Plugins > Installed Plugins.
- 3. Locate the 'Cost of Goods: Product Cost & Profit Calculator for WooCommerce' plugin.
- 4. Check the current installed version (displayed under the plugin name).
- 5. If the installed version is 4.1.0 or below, click 'Update Now' to install the latest available version.
- 6. After updating, verify the new version number reflects a release newer than 4.1.0.
- 7. Test the affected shortcodes ('alg_wc_cog_product_cost' and 'alg_wc_cog_product_profit') to ensure functionality remains intact.
- 8. Clear any caching plugins or server-side caches to ensure the patched code is served.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6962 — 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-2026-6962 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