dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-7613

HIGH · 7.2 CVSS v3.1 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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 Cost of Goods by PixelYourSite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'csvdata[0][cost_of_goods_value]' parameter in versions up to, and including, 1.2.12 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers 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 confidence

The Cost of Goods by PixelYourSite WordPress plugin up to version 1.2.12 contains a stored XSS vulnerability in the csvdata[0][cost_of_goods_value] parameter. Unauthenticated attackers can inject malicious JavaScript that persists in the database and executes when users access affected pages, due to missing input sanitization on intake and output escaping on display.

MitigationUpdate the plugin to a version beyond 1.2.12 that implements proper sanitization (such as sanitize_text_field) for the cost_of_goods_value parameter and output escaping (such as esc_html or esc_attr) when rendering the data.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Verify Cost of Goods plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Cost of Goods' or 'Cost of Goods (COG)' plugin. Note the version number displayed below the plugin name.
    Affected if The plugin is installed and version is 1.2.12 or lower
  2. Check the exact installed version
    Access the plugin files via FTP or file manager, open /wp-content/plugins/cost-of-goods/cost-of-goods.php and locate the 'Version:' header in the plugin comments at the top of the file.
    Affected if Version is 1.2.12 or below (any version up to and including 1.2.12)
  3. Identify if the vulnerable CSV import form is accessible
    Navigate to the plugin settings page in WordPress admin (usually under WooCommerce > Cost of Goods or a dedicated Cost of Goods menu). Look for a CSV import or bulk cost entry form that accepts 'csvdata[0][cost_of_goods_value]' input.
    Affected if The CSV import or bulk cost entry functionality is enabled and accessible
  4. Inspect the database for suspicious stored values
    Access the WordPress database via phpMyAdmin or command line. Query the postmeta or options tables for any entries containing script tags, javascript:, or onload/onerror attributes in fields that may store cost of goods data.
    Affected if Any stored XSS payloads (script tags, event handlers) are found in cost_of_goods related database fields

A user is affected if the Cost of Goods plugin is installed with version 1.2.12 or lower and the CSV import/bulk entry feature that uses the csvdata[0][cost_of_goods_value] parameter is in use or has been previously used.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 1.2.12 that implements proper sanitization (such as sanitize_text_field) for the cost_of_goods_value parameter and output escaping (such as esc_html or esc_attr) when rendering the data.

Recommended fix Moderate confidence

Version 1.2.13 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Cost of Goods by PixelYourSite' plugin
  4. 4. Check the current version installed (should be 1.2.12 or earlier)
  5. 5. Update the plugin to the latest available version (1.2.13 or later)
  6. 6. Alternatively, navigate to Dashboard > Updates and update all plugins
  7. 7. Verify the update was successful by checking the plugin version
Caveat Minor plugin update - review any settings changes after updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7613 — 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-2026-7613 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