dbcve.org
AprilWordPress extension · G5plus

CVE-2024-13419

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-02
Fix available
A fix is available. Upgrade to after 7.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Multiple plugins and/or themes for WordPress using Smart Framework are vulnerable to Stored Cross-Site Scripting due to a missing capability check on the saveOptions() and importThemeOptions() functions in various versions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update the plugin's settings which includes custom JavaScript that is enabled site-wide. This issue was escalated to Envato over two months from the date of this disclosure and the issue 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 confidence

Multiple WordPress plugins and themes using the Smart Framework contain a Stored XSS vulnerability due to missing capability checks on the saveOptions() and importThemeOptions() functions. Authenticated users with Subscriber-level access (the lowest WordPress role) can exploit these functions to modify plugin/theme settings, including injecting arbitrary JavaScript that executes site-wide when pages load.

MitigationAdd proper capability checks (e.g., 'manage_options') to the saveOptions() and importThemeOptions() functions to restrict access to administrators only, and sanitize any settings fields that accept JavaScript code before saving or outputting.

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
Affected:<= 5.1
AuteurWordPress extension
Affected:<= 7.1
BenaaWordPress extension
Affected:<= 4.0.0
BeyotWordPress extension
Affected:<= 6.0.6

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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. Identify installed G5plus theme
    Check your WordPress appearance/themes directory or plugin list for April, Auteur, Benaa, or Beyot themes. Note the exact version number displayed.
    Affected if One of these four themes is installed and its version is at or below the affected version (April <=5.1, Auteur <=7.1, Benaa <=4.0.0, Beyot <=6.0.6)
  2. Locate vulnerable functions in codebase
    Search theme files for 'saveOptions' and 'importThemeOptions' function definitions. Examine these functions for missing capability checks (look for 'manage_options' or similar admin-only capability validation).
    Affected if These functions exist and lack capability checks like 'manage_options' permission verification before executing
  3. Verify subscriber user role exists
    In WordPress admin, go to Users > All Users and confirm if any users have the Subscriber role assigned.
    Affected if Subscriber-level users exist in the WordPress installation
  4. Check theme option settings for malicious scripts
    Inspect the theme options database table (typically wp_options) or theme settings admin panel for any unexpected JavaScript, script tags, or onclick/onload attributes in option values.
    Affected if Arbitrary JavaScript code is present in theme/plugin settings values
  5. Test subscriber access to theme options
    Log in as a subscriber-level user and navigate to the theme options or settings page. Attempt to access the saveOptions or importThemeOptions functionality.
    Affected if Subscriber users can access and modify theme/plugin settings without restriction

You are affected if any of the four G5plus themes are installed at a vulnerable version AND subscriber users exist AND the vulnerable functions lack capability checks, allowing low-privilege users to inject JavaScript into settings.

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.

From vendor data
Upgrade available Upgrade to a release after 7.1
Interim mitigation

Add proper capability checks (e.g., 'manage_options') to the saveOptions() and importThemeOptions() functions to restrict access to administrators only, and sanitize any settings fields that accept JavaScript code before saving or outputting.

Fix this in April Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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