AprilWordPress extension · G5plus
CVE-2024-13418
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 · uneditedMultiple plugins and/or themes for WordPress are vulnerable to Arbitrary File Uploads due to a missing capability check on the ajaxUploadFonts() function in various versions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files that can make remote code execution possible. This issue was escalated to Envato over two months from the date of this disclosure and the issue, while partially patched, is still vulnerable.
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 confidenceThis is an arbitrary file upload vulnerability in multiple WordPress plugins and themes where the ajaxUploadFonts() function lacks proper capability checks. Authenticated attackers with Subscriber-level access (the lowest privilege level) can upload arbitrary files, potentially achieving remote code execution. The issue was reported to Envato but remains partially unpatched.
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
AprilWordPress extension
<= 5.1
AuteurWordPress extension
<= 7.1
BenaaWordPress extension
<= 4.0.0
BeyotWordPress extension
<= 6.0.6CVSS 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.
-
Identify installed G5plus themesList all installed WordPress themes in the wp-content/themes directory and identify any themes starting with 'april', 'auteur', 'benaa', or 'beyot' from the G5plus developerAffected if Any of these four themes are present in the themes directory
-
Check theme versionOpen the style.css file in each identified theme folder and locate the 'Version:' header to compare against the affected version ranges (April <= 5.1, Auteur <= 7.1, Benaa <= 4.0.0, Beyot <= 6.0.6)Affected if The installed version matches or is lower than the affected version for that specific theme
-
Locate vulnerable functionSearch theme source files (PHP) for the string 'ajaxUploadFonts' to determine if the vulnerable function is present in the codebaseAffected if The function ajaxUploadFonts is found in the theme files
-
Verify ajax action availabilityCheck if the theme registers the ajax action by searching for 'add_action' calls with 'wp_ajax_ajaxUploadFonts' or similar patterns in the theme PHP filesAffected if The ajax action for file upload is registered and accessible
-
Confirm low-privilege accessIn the WordPress admin under Users > Roles, verify if the 'Subscriber' role exists and has access to the site, as this role can exploit the vulnerability if the above conditions are metAffected if Subscriber-level users exist and can access the site frontend or backend
A user is affected if they have any of the four G5plus themes (April, Auteur, Benaa, or Beyot) installed at or below the specified version AND the ajaxUploadFonts function exists in their theme files, creating a path forSubscriber-level attackers to upload arbitrary files.
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 dataIdentify and update all affected WordPress plugins/themes from the Envato marketplace; if patches are unavailable, consider removing or disabling the vulnerable components until a full fix is released.
Fix this in April
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13418 — 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-2024-13418 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