dbcve.org
Hero Banner UltimateWordPress extension · Essentialplugin

CVE-2022-45818

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-04
Fix available
A fix is available. Upgrade to after 1.3.4 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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in WP OnlineSupport, Essential Plugin Hero Banner Ultimate plugin <= 1.3.4 versions.

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

Authenticated users with contributor+ privileges can inject malicious JavaScript through the Hero Banner Ultimate WordPress plugin. The payload is stored in the database and executes when other users (including administrators) view affected pages in the admin dashboard or frontend.

MitigationUpdate Hero Banner Ultimate plugin to a version newer than 1.3.4. If no update is available, remove the plugin and seek an alternative solution.

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
Hero Banner UltimateWordPress extension
Affected:<= 1.3.4

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. Confirm Hero Banner Ultimate plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Hero Banner Ultimate' by Essentialplugin, or check if the directory /wp-content/plugins/hero-banner-ultimate/ exists on the server
    Affected if Plugin is present on the site
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find Hero Banner Ultimate and read the version number from the plugin description, or open the main plugin PHP file and check the 'Version' header in the plugin comment block
    Affected if Version is 1.3.4 or lower
  3. Identify if any Hero Banners exist
    In the WordPress admin dashboard, look for a 'Hero Banner' menu item and list all created banners, or query the wp_posts table for post_type='hero_banner' entries
    Affected if Any banner posts exist in the database AND the plugin version is vulnerable
  4. Inspect stored banner content for malicious scripts
    Examine the content of each hero banner (in admin preview or by querying wp_posts and related meta tables) for suspicious elements such as script tags, iframe tags, object tags, or HTML event handlers (onload, onerror, onmouseover, etc.)
    Affected if Any hero banner content contains JavaScript code, iframes, or suspicious HTML that was not intentionally added by an administrator

A user is affected if the Hero Banner Ultimate plugin version is 1.3.4 or lower AND any hero banner entries in the database contain embedded JavaScript or iframe code that could execute when viewed by other users.

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 a release after 1.3.4
Interim mitigation

Update Hero Banner Ultimate plugin to a version newer than 1.3.4. If no update is available, remove the plugin and seek an alternative solution.

Recommended fix Moderate confidence

Latest available version in WordPress plugin repository (version > 1.3.4)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Hero Banner Ultimate' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running on a version higher than 1.3.4
  6. 6. Test the plugin functionality to ensure the update does not break existing features

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

Fix this in Hero Banner Ultimate Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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