Sql Chart Builder
Approved changes feed: RSS · Atom
cpe:2.3:a:elvinhaci:sql_chart_builder:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Elvinhaci (e9524733-f7d8-56d3-bf19-dccddfccd81a) |
|---|---|
| Product | Sql Chart Builder (348c6d95-a94c-553d-8f89-5fa96fb4f458) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-100158 |
vulnerable | 2026-11-03 10:15:32.946638 |
SQL Chart Builder <= 3.0.6 - Authenticated (Subscriber+) Stored Cross-Site Scripting via SQL Chart Label (X-axis) via Stored User Field
MEDIUM (6.4)
The SQL Chart Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'X-axis column value ($value->$xarg_s from $wpdb->get_results())' parameter in all versions up to, and including, 3.0.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an administrator to have published a chart whose SQL query returns a column controllable by a lower-privileged user, such as wp_users.display_name, which a Subscriber can populate with a payload via the standard WordPress profile page at /wp-admin/profile.php.
Published: 2026-10-16T05:30:19.302Z
Updated: 2026-10-16T14:39:05.141Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-11430 |
vulnerable | 2026-06-08 06:23:49.639979 |
SQL Chart Builder <= 2.3.6 - Authenticated (Contributor+) SQL Injection
MEDIUM (6.5)
The SQL Chart Builder plugin for WordPress is vulnerable to SQL Injection via the 'arg1' arg of the 'gvn_schart_2' shortcode in all versions up to, and including, 2.3.6 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Published: 2024-12-12T03:23:04.994Z
Updated: 2026-04-08T16:41:02.096Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.