dbcve.org
LayersliderWordPress extension · Kreaturamedia

CVE-2023-47785

HIGH · 8.8 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to 7.7.10 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in LayerSlider plugin <= 7.7.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 · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the LayerSlider WordPress plugin versions 7.7.9 and below allows attackers to induce authenticated users to perform unintended administrative actions by tricking them into submitting malicious requests.

MitigationUpgrade LayerSlider to a version newer than 7.7.9 which should include anti-CSRF token validation for state-changing operations.

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
LayersliderWordPress extension
Affected:< 7.7.10

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Check if LayerSlider plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'LayerSlider' or 'Kreaturamedia Layerslider'. Alternatively, check the /wp-content/plugins/LayerSlider/ directory exists.
    Affected if LayerSlider plugin is not found in the WordPress installation
  2. Identify the installed LayerSlider version
    In WordPress admin, go to LayerSlider > About (or check the plugin file header in /wp-content/plugins/Layerslider/layerslider.php for the 'Version' comment).
    Affected if The installed version is 7.7.9 or lower (below 7.7.10)
  3. Verify the WordPress user authentication state
    This CSRF vulnerability affects authenticated administrators. Confirm that administrative users have active sessions.
    Affected if Administrative users are authenticated and the vulnerable plugin version is in use

You are affected if LayerSlider plugin version 7.7.9 or lower is installed and running on your WordPress site, allowing attackers to exploit CSRF against authenticated administrators.

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

Upgrade LayerSlider to a version newer than 7.7.9 which should include anti-CSRF token validation for state-changing operations.

Recommended fix High confidence

LayerSlider 7.7.10

  1. Navigate to the WordPress admin dashboard
  2. Go to the LayerSlider plugin settings or WordPress plugin repository
  3. Update LayerSlider to version 7.7.10 or later
  4. Verify the update was successful

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

Fix this in Layerslider Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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