CVE-2024-1533
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 · uneditedThe Shortcodes and extra features for Phlox theme plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the HTML Element in all versions up to, and including, 2.15.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access or higher, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Requires Elementor and the Phlox theme to be installed.
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 confidenceThe Shortcodes and extra features for Phlox theme plugin for WordPress contains a stored XSS vulnerability in its HTML Element feature. Due to insufficient input sanitization and output escaping, authenticated users with contributor-level access or higher can inject arbitrary JavaScript into pages. This malicious script executes whenever other users access those pages, enabling session hijacking, credential theft, or defacement.
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< 2.15.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'Averta Shortcodes' or 'Phlox' or 'Shortcodes and Extra Features For Phlox Theme'. Confirm the plugin appears in the list.Affected if The plugin is present in the WordPress installation
-
Check the installed versionIn the Plugins list, locate the plugin and view the version number displayed beneath the plugin name. Compare this version to the affected range: any version below 2.15.8 is vulnerable.Affected if The installed version is lower than 2.15.8
-
Identify if the HTML Element feature is in useAccess the WordPress admin panel and look for the plugin settings or a feature called 'HTML Element', 'HTML', or 'Custom HTML' within the plugin options. Alternatively, search the WordPress database in wp_posts for shortcodes or content containing the plugin's HTML Element markup.Affected if The HTML Element feature has been used to create or embed content in any post, page, or widget
-
Inspect published content for injected scriptsReview pages and posts that use the HTML Element feature by manually viewing them or searching the database wp_posts table for script tags, javascript: URIs, or onload/onerror event handlers within the post_content field.Affected if Any page or post contains unexpected script tags, event handlers, or suspicious JavaScript that was not intentionally added by an administrator
A user is affected if the Averta Shortcodes plugin version is below 2.15.8 AND the HTML Element feature has been used to create content that could contain injected malicious scripts.
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.
dbcve · scoped2.15.8
Update the plugin to a version beyond 2.15.7 once available. Additionally, audit existing pages using the HTML Element for any injected malicious scripts and remove them, as the vulnerability is stored.
2.15.8
- Backup your WordPress database and files before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Find 'Shortcodes and Extra Features for Phlox Theme' in the plugin list
- Click 'Update now' or manually update to version 2.15.8
- Verify the plugin shows version 2.15.8 after updating
- Clear any site caching if using a caching plugin
- Confirm the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-1533 — 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-1533 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