dbcve.org
Smart Slider 3WordPress extension · Nextendweb

CVE-2022-45843

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-23
Fix available
A fix is available. Upgrade to 3.5.1.11 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 vulnerability in Nextend Smart Slider 3 plugin <= 3.5.1.9 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 · moderate confidence

Authenticated users with contributor-level permissions or higher can inject malicious JavaScript through the Nextend Smart Slider 3 plugin settings. The injected script is stored persistently and executes when other users access affected slider pages, exploiting insufficient input sanitization on plugin configuration fields.

MitigationUpdate the Nextend Smart Slider 3 plugin to a version newer than 3.5.1.9. If no patched version is available, restrict user role permissions or disable the plugin until a fix is released.

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
Smart Slider 3WordPress extension
Affected:< 3.5.1.11

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 Smart Slider 3 plugin is installed
    Check your WordPress plugins directory or admin panel for 'Nextend Smart Slider 3' or 'Nextendweb Smart Slider 3' in the list of active plugins
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number displayed for Smart Slider 3, or check the plugin's main PHP file for the 'Version' header comment
    Affected if The version number is lower than 3.5.1.11 (e.g., 3.5.1.10, 3.5.0.x, etc.)
  3. Inspect slider configuration fields for unsanitized input
    Access the Smart Slider 3 settings panel (usually under 'Smart Slider' in the admin menu) and review any text fields in slider settings, global settings, or individual slide configurations for unusual characters or script tags
    Affected if Script tags (<script>), JavaScript event handlers (onclick, onerror, etc.), or encoded malicious payloads are present in configuration fields
  4. Review recent plugin settings changes
    Check WordPress activity logs, audit logs, or revision history for Smart Slider 3 settings modified by users with contributor-level or higher permissions
    Affected if Settings were modified by a user with contributor, author, editor, or admin role within recent activity logs

Your environment is affected if Smart Slider 3 version is below 3.5.1.11 AND the plugin is active with contributor-level users having access to its settings, as the vulnerability allows persistent JavaScript injection through those configuration fields.

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

Update the Nextend Smart Slider 3 plugin to a version newer than 3.5.1.9. If no patched version is available, restrict user role permissions or disable the plugin until a fix is released.

Recommended fix High confidence

Smart Slider 3 version 3.5.1.11

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Smart Slider 3' in the plugin list
  4. If an update is available, click 'Update Now' to update to version 3.5.1.11 or later
  5. Alternatively, upload and install Smart Slider 3 version 3.5.1.11 or newer manually from wordpress.org/plugins/smart-slider-3
  6. Verify the plugin version shows 3.5.1.11 or higher after update

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

Fix this in Smart Slider 3 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-2022-45843 — 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-45843 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