dbcve.org
All In One FaviconWordPress extension · Grimmdude

CVE-2023-24416

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-23
Fix available
A fix is available. Upgrade to 4.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Arne Franken All In One Favicon.This issue affects All In One Favicon: from n/a through 4.7.

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 confidence

A path traversal vulnerability in the All In One Favicon WordPress plugin allows attackers to access files outside the restricted web root directory through manipulated file path inputs. The vulnerability stems from insufficient validation of user-supplied path parameters, potentially enabling unauthorized file reads.

MitigationUpgrade to a patched version of the plugin that includes proper path validation and sanitization. If no patch is available, implement input validation to ensure all file paths remain within the intended directory using canonicalization checks.

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
All In One FaviconWordPress extension
Affected:< 4.8

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the All In One Favicon plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'all-in-one-favicon' or check the WordPress admin under Plugins > Installed Plugins for 'All In One Favicon' by Grimmdude
    Affected if The plugin folder exists in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin file (usually all-in-one-favicon.php or similar) in the plugin folder and look for the version comment/header, or check the WordPress plugin database entry for the version number
    Affected if The version number is less than 4.8 or no version is displayed (plugin may be unlisted but still present)
  3. Verify the plugin is active
    Check WordPress admin under Plugins > Installed Plugins to confirm the All In One Favicon plugin shows as 'Active'
    Affected if The plugin is currently activated on the WordPress site
  4. Check if the plugin handles file paths
    Review the plugin settings page under Settings > All In One Favicon (or similar) to see if the plugin allows configuring favicon file paths or uploading custom icons
    Affected if The plugin allows custom path configuration or file uploads where user-supplied paths could be processed

You are affected if the All In One Favicon plugin is installed, active, and running version 4.7 or lower, as these versions lack proper path validation for user-supplied file path inputs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.8 or later
Fixed in 4.8
Interim mitigation

Upgrade to a patched version of the plugin that includes proper path validation and sanitization. If no patch is available, implement input validation to ensure all file paths remain within the intended directory using canonicalization checks.

Recommended fix Moderate confidence

All In One Favicon version 4.8

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Locate 'All In One Favicon' plugin
  4. Click 'Update now' or upload version 4.8 of the plugin
  5. Verify the plugin version is 4.8 after update
  6. Test that the favicon functionality works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in All In One Favicon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24416 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-24416 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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