Shockingly Simple FaviconWordPress extension · Matiass
CVE-2023-44246
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Matias s Shockingly Simple Favicon plugin <= 1.8.2 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the 'Shockingly Simple Favicon' WordPress plugin versions 1.8.2 and earlier allows attackers to trick authenticated administrators into performing unintended actions (such as modifying plugin settings) by leveraging the lack of proper CSRF token validation on plugin admin pages.
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
Shockingly Simple FaviconWordPress extension
<= 1.8.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 plugin is installedCheck your WordPress plugins directory or wp-admin plugins list for 'Shockingly Simple Favicon' by Matiass, or query the wp_plugins database table for the plugin slugAffected if The plugin is not present in the WordPress installation, then the vulnerability does not apply
-
Confirm installed versionIn WordPress admin, go to Plugins > Installed Plugins > Shockingly Simple Favicon and check the version number displayed, or inspect the plugin header in its main PHP file (typically shockingly-simple-favicon.php)Affected if Version is 1.8.2 or lower - this places the plugin within the affected version range
-
Identify plugin admin endpointsAccess the plugin settings page in wp-admin (usually under Settings or a dedicated menu item for this plugin), noting the URL paths used for form actionsAffected if Admin can access plugin settings pages without authentication being bypassed - CSRF requires an authenticated admin session to be exploited
-
Inspect form submissions for nonce validationExamine the plugin's PHP source code for form handlers in admin areas. Search for presence of 'wp_nonce_field', 'check_admin_referer', or 'verify_nonce' calls in functions handling form submissionsAffected if Form handlers in the plugin lack nonce verification code - the absence of these calls indicates the CSRF protection is missing
-
Check AJAX handlers for CSRF protectionReview any AJAX action handlers registered by the plugin (search for 'add_action' with 'wp_ajax') and verify they include nonce validation using 'check_ajax_referer' or similar validation functionsAffected if AJAX endpoints registered by the plugin do not validate nonces - these endpoints can be abused via CSRF to modify plugin settings
Your environment is affected if the Shockingly Simple Favicon plugin is installed at version 1.8.2 or lower and its admin forms or AJAX handlers lack proper nonce/CSRF token validation.
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.
From vendor dataUpdate the plugin to the latest version which includes anti-CSRF token validation, or implement proper nonce verification on all form submissions and AJAX actions within the plugin.
Fix this in Shockingly Simple Favicon
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44246 — 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-44246 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