dbcve.org
Slider Responsive SlideshowWordPress extension · Awplife

CVE-2024-35722

HIGH · 8.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 1.4.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Missing Authorization vulnerability in A WP Life Slider Responsive Slideshow – Image slider, Gallery slideshow.This issue affects Slider Responsive Slideshow – Image slider, Gallery slideshow: from n/a through 1.4.0.

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

Missing authorization vulnerability in the WordPress plugin 'Slider Responsive Slideshow – Image slider, Gallery slideshow' up to version 1.4.0 allows unauthenticated or unauthorized users to access privileged functionality within the plugin, likely due to missing capability checks or nonce validations on sensitive AJAX actions or admin pages.

MitigationUpdate the plugin to the latest available version which should contain proper authorization checks; if no update exists, consider removing the plugin until a patched version 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
Slider Responsive SlideshowWordPress extension
Affected:< 1.4.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Slider Responsive Slideshow - Image slider, Gallery slideshow' (or 'Awplife Slider Responsive Slideshow'). Confirm the plugin appears in the list.
    Affected if The plugin is installed and active in WordPress.
  2. Check installed version number
    On the Plugins page, find the plugin and note the version number displayed below the plugin name. Compare this to the affected range: versions prior to 1.4.2 are vulnerable.
    Affected if The installed version is 1.4.1 or lower (anything less than 1.4.2).
  3. Confirm plugin is active
    On the Plugins page, verify the plugin is activated (the plugin will show a 'Deactivate' link rather than 'Activate' if it is currently running).
    Affected if The plugin is both installed AND activated.
  4. Audit user access and roles
    Review WordPress users and roles in Users > All Users. Look for any unexpected administrator accounts or modifications to user capabilities that may have been created through the vulnerable plugin's unauthorized functionality.
    Affected if Unexpected users or role changes exist that were not created by legitimate administrators.

If the Awplife Slider Responsive Slideshow plugin is installed, active, and running version 1.4.1 or lower, the environment is vulnerable to unauthorized access.

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

Update the plugin to the latest available version which should contain proper authorization checks; if no update exists, consider removing the plugin until a patched version is released.

Recommended fix High confidence

1.4.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Slider Responsive Slideshow' in the plugin list
  4. Check if the current version is below 1.4.2
  5. If vulnerable, click 'Update Now' to update to the latest version, or manually upload version 1.4.2 or higher from the WordPress plugin repository
  6. Verify the update was successful by checking the plugin version

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

Fix this in Slider Responsive Slideshow Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-2024-35722 — 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-2024-35722 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