Biggopti Library (Various Versions) - Cross-Site Scripting via display_id from Sigmative API

2026-08-08 00:00
Anonymous

Strategic Overview

Status
Patched in 3.0.8
Affected Plugin
Ultimate Store Kit – Addon For WooCommerce, EDD and Elementor
Affected Version
<= 3.0.7
CVSS
5.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all Ultimate Store Kit – Addon For WooCommerce, EDD and Elementor vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Ultimate Store Kit WordPress plugin, affecting versions <= 3.0.7. It carries a CVSS score of 5.4 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 3.0.8; sites on affected versions should update now. Disclosed August 2026.

Vulnerability Overview

The Biggop Library is vulnerable to Cross-Site Scripting via the ‘display_id’ parameter from the Sigmative API in various versions due to insufficient output escaping. This makes it possible for attackers who can compromise the Sigmative API server to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Ultimate Store Kit <= 3.0.7 carries this weakness at display_id, and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Ultimate Store Kit the fix is 3.0.8: builds <= 3.0.7 are affected, anything from 3.0.8 onward is not.

Remediation

Update to version 3.0.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Ultimate Store Kit: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Ultimate Store Kit 3.0.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/7bf1d6f9-afe2-41c2-968b-20dbc474cd73

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C