dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-6309

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
The Attachment File Icons (AF Icons) plugin for WordPress is vulnerable to Cross-Site Request Forgery to Arbitrary File Upload in versions up to, and including, 1.3. This is due to missing nonce validation in the 'afi_overview' function and missing file type validation in the 'upload_icons' function. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 · high confidence

The Attachment File Icons plugin for WordPress fails to validate nonces in the afi_overview function, allowing CSRF attacks, and lacks file type validation in upload_icons, enabling unauthenticated attackers to upload arbitrary files including executable code. This combination can lead to remote code execution if a site administrator can be tricked into triggering the malicious upload request.

MitigationUpdate the plugin to the latest patched version immediately; if no patch exists, disable and remove the plugin, then audit the site for any maliciously uploaded files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
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 checks

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

  1. Verify Attachment File Icons plugin is installed
    Check your WordPress plugins directory or access the Plugins page in wp-admin to confirm the Attachment File Icons plugin is active
    Affected if the plugin is installed and active
  2. Identify the installed plugin version
    Locate the plugin header in wp-content/plugins/attachment-file-icons/attachment-file-icons.php or view the plugin details in WordPress admin under Plugins > Installed Plugins
    Affected if the installed version matches the vulnerable version range or cannot be determined (treat as vulnerable)
  3. Inspect uploaded files directory for suspicious content
    Check the upload directory (typically wp-content/uploads/) for any recently added PHP files, shell scripts, or executable files that were not intentionally uploaded by an administrator
    Affected if unexpected executable files exist in upload directories
  4. Review server access logs for upload activity
    Examine HTTP access logs for POST requests to the upload_icons endpoint or similar plugin URLs originating from unauthenticated or unexpected sources
    Affected if unauthenticated file upload requests are present in the logs
  5. Check for newly created admin accounts
    Review the wp_users table in the database for unfamiliar administrator accounts or verify all expected admin accounts in WordPress user management
    Affected if unexpected administrator accounts exist in the database

A user is affected if the Attachment File Icons plugin is installed and the version is within the vulnerable range, or if unexpected executable files appear in upload directories indicating potential exploitation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest patched version immediately; if no patch exists, disable and remove the plugin, then audit the site for any maliciously uploaded files.

Recommended fix Moderate confidence

Latest version > 1.3 (check wordpress.org for current stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Attachment File Icons (AF Icons)' plugin
  4. Check if an update is available and click 'Update Now'
  5. Alternatively, manually download the latest version from wordpress.org/plugins/attachment-file-icons/ and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the new version number reflects the fix

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6309 — 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-2024-6309 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