PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-108073 SureCart CVE debrief

The SureCart WordPress plugin before 4.9.5 does not restrict which related objects an anonymous visitor may include when reading a single upsell funnel through its REST API, nor strip private fields from those objects, allowing unauthenticated users to read merchant-private catalog data such as pricing, commission, stock, SKU and tax internals, including unpublished products.

Vendor
SureCart
Product
SureCart
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-21
Original CVE updated
2026-10-21
Advisory published
2026-10-21
Advisory updated
2026-10-21

Who should care

Defenders responsible for WordPress installations with the SureCart plugin should assess exposure and prioritize remediation. This includes reviewing the affected versions, assessing the potential impact on their systems, and verifying the vendor's advisory. Additionally, security teams and vulnerability management teams should be aware of this vulnerability and its potential impact on their organization's systems.

Why it matters

Defenders should care about CVE-2026-108073 because it allows unauthenticated users to read private catalog data, potentially exposing sensitive information.

  • Unauthenticated access to merchant-private catalog data
  • Potential exposure of sensitive data such as pricing and stock levels
  • Need for verification of affected versions and remediation

Technical summary

The SureCart WordPress plugin before 4.9.5 does not restrict which related objects an anonymous visitor may include when reading a single upsell funnel through its REST API, nor strip private fields from those objects, allowing unauthenticated users to read merchant-private catalog data such as pricing, commission, stock, SKU and tax internals, including unpublished products. This vulnerability allows unauthenticated access to sensitive information, potentially exposing merchant-private data. Defenders should assess the impact of this vulnerability on their systems and prioritize remediation.

Defensive priority

Defenders should prioritize verifying and upgrading to version 4.9.5 or later, and restrict access to sensitive catalog data.

Recommended defensive actions

  • Verify and upgrade to version 4.9.5 or later
  • Restrict access to sensitive catalog data
  • Monitor for unauthorized access to catalog data
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, but limited information is available on affected versions and remediation. Defenders should verify the affected versions, review the vendor's advisory, and assess the potential impact on their systems. The SureCart plugin's REST API allows unauthenticated access to private catalog data, including pricing, commission, stock, SKU, and tax internals. This vulnerability affects WordPress installations with the SureCart plugin before version 4.9.5.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-108073 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-108073

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-108073 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-108073

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.