Custom Field Suite
Approved changes feed: RSS · Atom
cpe:2.3:a:custom_field_suite_project:custom_field_suite:0:*:*:*:*:*:*:*part: a version: 0 update: *
| Vendor | Custom Field Suite Project (1f906692-aac4-58e1-99fe-76fa85bece6c) |
|---|---|
| Product | Custom Field Suite (0f39ff0f-e5b3-59b2-b201-95ef84f517d3) |
| 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-2024-3561 |
vulnerable | 2026-06-08 06:41:53.582894 |
Custom Field Suite <= 2.6.7 - Authenticated (Contributor+) SQL Injection via Term Custom Field
HIGH (8.8)
The Custom Field Suite plugin for WordPress is vulnerable to SQL Injection via the the 'Term' custom field in all versions up to, and including, 2.6.7 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-06-20T02:08:27.298Z
Updated: 2026-04-08T17:15:39.721Z Reference links
|
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.