dbcve.org
Media SliderWordPress extension · Awplife

CVE-2024-35717

HIGH · 8.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 1.4.0 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 Media Slider – Photo Sleder, Video Slider, Link Slider, Carousal Slideshow.This issue affects Media Slider – Photo Sleder, Video Slider, Link Slider, Carousal Slideshow: from n/a through 1.3.9.

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

This is a missing authorization vulnerability in the 'A WP Life Media Slider' WordPress plugin (versions through 1.3.9). The vulnerability allows attackers to access functionality or data without proper authorization checks, likely due to missing capability checks or nonce validations on sensitive AJAX endpoints within the plugin.

MitigationUpdate the Media Slider plugin to the latest version beyond 1.3.9 once available, or implement proper authorization checks (current_user_can() and nonce verification) on all AJAX handlers and admin pages in the plugin.

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
Media SliderWordPress extension
Affected:< 1.4.0

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 Awplife Media Slider plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Awplife Media Slider' or check the plugin files in wp-content/plugins/awplife-media-slider/ for the main plugin file containing the version header
    Affected if Plugin is installed and version is below 1.4.0 (1.3.9 or lower)
  2. Locate AJAX handler registrations
    Examine the main plugin PHP file for add_action calls registering AJAX handlers, looking for patterns like 'wp_ajax_awplife_*' or 'wp_ajax_nopriv_awplife_*'
    Affected if AJAX endpoints are registered without proper capability checks (no current_user_can() call before executing the handler)
  3. Inspect AJAX handler functions for authorization
    Open the PHP files containing the AJAX callback functions identified in step 2 and verify they include current_user_can() or similar authorization checks at the function entry point
    Affected if AJAX handlers execute sensitive operations without verifying user capabilities first
  4. Check for nonce validation in AJAX handlers
    Search the AJAX callback functions for wp_verify_nonce() or check_admin_referer() calls before processing any data
    Affected if AJAX handlers process requests without validating nonces, allowing CSRF attacks

If the Awplife Media Slider plugin version is below 1.4.0 and its AJAX endpoints lack current_user_can() capability checks or nonce validation, the environment is affected by this missing authorization vulnerability.

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.0 or later
Fixed in 1.4.0
Interim mitigation

Update the Media Slider plugin to the latest version beyond 1.3.9 once available, or implement proper authorization checks (current_user_can() and nonce verification) on all AJAX handlers and admin pages in the plugin.

Recommended fix High confidence

Media Slider plugin version 1.4.0 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Media Slider – Photo Sleder, Video Slider, Link Slider, Carousal Slideshow'
  4. Check if the current version is below 1.4.0
  5. If vulnerable, click 'Update Now' to upgrade to version 1.4.0 or later
  6. Alternatively, download version 1.4.0 from the WordPress Plugin Repository and upload manually
  7. After update, verify the new version is 1.4.0 or higher

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

Fix this in Media Slider Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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