CVE-2023-46084
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in bPlugins LLC Icons Font Loader allows SQL Injection.This issue affects Icons Font Loader: from n/a through 1.1.2.
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 · moderate confidenceSQL injection vulnerability in bPlugins LLC Icons Font Loader plugin allows remote attackers to inject malicious SQL commands via unsanitized user input that is directly incorporated into database queries. This could enable attackers to extract, modify, or delete database contents, potentially compromising the WordPress installation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.1.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Icons Font Loader plugin is installedNavigate to WordPress admin > Plugins and confirm whether the Icons Font Loader plugin by bPlugins LLC appears in the installed plugins listAffected if Plugin is present in the WordPress installation
-
Check installed version numberOn the Plugins page, click on Icons Font Loader to view the version details, or inspect the plugin header in its main PHP file for the Version fieldAffected if Installed version is 1.1.2 or lower
-
Identify SQL query locations using user inputExamine plugin PHP files for database query functions (such as $wpdb->prepare, $wpdb->query, or direct SELECT/INSERT/UPDATE statements) that incorporate $_GET, $_POST, or $_REQUEST superglobals without proper sanitizationAffected if User-supplied input is used directly in SQL queries without prepared statements or escaping
If Icons Font Loader is installed with version 1.1.2 or lower and contains SQL queries that directly use unsanitized user input, the environment is affected by CVE-2023-46084
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement prepared statements/parameterized queries for all database operations and validate/sanitize all user-supplied input before using it in SQL queries.
Version 1.1.3 or later
- 1. Backup your WordPress site before making any changes
- 2. Navigate to the WordPress admin dashboard
- 3. Go to Plugins > Installed Plugins
- 4. Find "Icons Font Loader" by bPlugins LLC
- 5. If an update is available, click "Update Now"
- 6. Alternatively, download the latest version from the WordPress Plugin Directory and upload it manually
- 7. Verify the plugin updated successfully by checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46084 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-46084 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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