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

CVE-2024-4218

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The AffiEasy plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.6. This is due to plugin improperly releasing the tagged and patched version of the plugin - the vulnerable version is used as the core files, while the patched version was included in a 'trunk' folder. This makes it possible for unauthenticated attackers to perform a variety of actions 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 · moderate confidence

The AffiEasy WordPress plugin up to version 1.1.6 contains a Cross-Site Request Forgery (CSRF) vulnerability. The issue stems from an improper release process where the vulnerable version remained as the core plugin files while the patched version was only placed in a 'trunk' folder but not deployed. This allows unauthenticated attackers to forge administrative actions by tricking site admins into clicking malicious links.

MitigationUpdate to the properly patched version of the AffiEasy plugin once available, and implement WordPress nonces/CSRF tokens for admin actions to prevent forged request attacks.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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 AffiEasy plugin installation
    Check your WordPress site's wp-content/plugins/ directory for a folder named 'affieasy' or similar. You can also list installed plugins via WP-CLI: wp plugin list --search=affiEasy
    Affected if The AffiEasy plugin folder exists in the plugins directory
  2. Determine the installed version
    Open the main plugin file (usually affieasy.php) in the plugin folder and locate the 'Version:' field in the plugin header comment at the top. Alternatively, check the readme.txt file for the 'Stable tag' entry
    Affected if The reported version is 1.1.6 or lower
  3. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm AffiEasy is activated, or use WP-CLI: wp plugin status affieasy
    Affected if The plugin is installed and currently active on the site
  4. Check for CSRF protection in admin actions
    Review the plugin's PHP files for admin action handlers (functions hooked to admin_init, admin_post, or similar). Look for presence of wp_verify_nonce(), check_admin_referer(), or wp_nonce_field() calls in functions that perform state-changing operations
    Affected if Admin action functions lack nonce verification and are reachable without CSRF tokens
  5. Confirm the trunk vs core deployment issue
    If accessible via FTP or file manager, check whether a 'trunk' folder exists alongside the main plugin files. The vulnerability exists because the patched version was placed in trunk but not deployed to the main plugin directory
    Affected if The plugin directory structure shows a trunk folder with different version files than the deployed core files, or the core files remain at version 1.1.6 or below

Your environment is affected if the AffiEasy WordPress plugin is installed with version 1.1.6 or lower and lacks proper nonce/CSRF token validation on administrative actions.

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 to the properly patched version of the AffiEasy plugin once available, and implement WordPress nonces/CSRF tokens for admin actions to prevent forged request attacks.

Recommended fix Moderate confidence

Latest version of AffiEasy plugin (beyond 1.1.6)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the AffiEasy plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is newer than 1.1.6

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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