dbcve.org
Shortcodes And Extra Features For Phlox ThemeWordPress extension · Averta

CVE-2024-3341

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 2.15.8 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
The Shortcodes and extra features for Phlox theme plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'aux_gmaps' shortcode in all versions up to, and including, 2.15.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Shortcodes and extra features for Phlox theme plugin for WordPress contains a stored XSS vulnerability in the 'aux_gmaps' shortcode. Due to insufficient input sanitization and output escaping on user-supplied attributes, authenticated attackers with contributor-level access can inject arbitrary JavaScript that executes whenever users access injected pages.

MitigationUpdate the plugin to a version beyond 2.15.7 that implements proper sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_html) for all shortcode attributes.

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
Shortcodes And Extra Features For Phlox ThemeWordPress extension
Affected:< 2.15.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
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. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Shortcodes and Extra Features for Phlox Theme' or 'Averta Shortcodes And Extra Features For Phlox Theme'. Note whether it is active or not.
    Affected if The plugin is installed and active, and the version is below 2.15.8
  2. Check the installed version number
    On the Plugins page, find the plugin and locate the version number displayed below the plugin name. Compare this against the affected range: any version below 2.15.8 is vulnerable.
    Affected if The installed version is any version lower than 2.15.8 (e.g., 2.15.7, 2.15.6, etc.)
  3. Identify usage of the aux_gmaps shortcode
    Search your WordPress database for content containing '[aux_gmaps' shortcode. You can use phpMyAdmin or run a SQL query: SELECT * FROM wp_posts WHERE post_content LIKE '%[aux_gmaps%' (adjust prefix if wp_ is different).
    Affected if Any post or page contains the aux_gmaps shortcode in its content, regardless of attributes used
  4. Inspect shortcode attributes for potential XSS payloads
    For each post containing aux_gmaps, examine the shortcode attributes (such as address, lat, lng, or similar parameters). Look for unusual characters like <script>, javascript:, onload=, onerror=, or other HTML/script tags.
    Affected if The shortcode attributes contain unsanitized script tags, event handlers (onclick, onerror, etc.), or javascript: URIs

You are affected if the Averta Shortcodes And Extra Features For Phlox Theme plugin is installed with a version below 2.15.8 and any page or post contains the aux_gmaps shortcode with malicious attributes.

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 2.15.8 or later
Fixed in 2.15.8
Interim mitigation

Update the plugin to a version beyond 2.15.7 that implements proper sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_html) for all shortcode attributes.

Recommended fix High confidence

2.15.8

  1. Update the Shortcodes And Extra Features For Phlox Theme plugin to version 2.15.8 or later through the WordPress plugin dashboard or via wp-cli: wp plugin update aux-elements

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

Fix this in Shortcodes And Extra Features For Phlox Theme 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-2024-3341 — 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-3341 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