CVE-2026-57737
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Averta LTD Shortcodes and extra features for Phlox theme allows DOM-Based XSS. This issue affects Shortcodes and extra features for Phlox theme: from n/a through 2.17.16.
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 confidenceDOM-Based XSS vulnerability in the Shortcodes and extra features for Phlox theme allows attackers to inject malicious scripts through unsanitized user input that gets executed client-side in the browser. This occurs when the plugin processes and renders shortcode content without proper output encoding.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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 if Phlox shortcodes plugin is installedCheck your WordPress installation for the 'Shortcodes and extra features for Phlox' theme/plugin. This is typically found in wp-content/plugins/auxin-shortcodes or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'Shortcodes and extra features for Phlox' or 'Auxin Shortcodes'.Affected if The plugin is present in the installation
-
Determine the installed plugin versionIn WordPress admin, navigate to Plugins > Installed Plugins, find the Phlox shortcodes plugin, and read the version number from the plugin description. Alternatively, check the plugin's main PHP file header for the 'Version' tag.Affected if The version is 2.17.16 or earlier, or if no version is displayed and the plugin has not been updated recently
-
Check active shortcodes that accept user inputReview your WordPress pages, posts, and widget areas for shortcodes that process user-supplied content. Look for any custom or theme-specific shortcodes that might render content directly to the DOM without encoding. Search post content for shortcode syntax like [shortcode_name] and identify which ones handle user-controlled data.Affected if Shortcodes that render unsanitized user input to the page are actively in use
-
Inspect rendered output for unsanitized contentView the source of a page using the suspected shortcode in a browser. Look for any user-provided data appearing directly in HTML without being escaped (for example, look for <script> tags, event handlers like onclick=, or unencoded < > characters in user input fields).Affected if User input appears in the HTML output without proper encoding (such as <script> showing as literal text vs. encoded)
You are affected if the Shortcodes and extra features for Phlox plugin is installed with version 2.17.16 or earlier AND shortcodes that process user input are actively used on your site.
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 dataUpdate Shortcodes and extra features for Phlox theme to a version beyond 2.17.16 which should contain the patch. If no update is available, implement output encoding on all user-controlled data before rendering to the DOM and review shortcode handlers for proper sanitization.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57737 — 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-2026-57737 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