dbcve.org
Post Grid\, Slider \& Carousel UltimateWordPress extension · Wpwax

CVE-2025-24782

HIGH · 8.8 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 1.7 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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in wpWax Post Grid, Slider & Carousel Ultimate post-grid-carousel-ultimate allows PHP Local File Inclusion.This issue affects Post Grid, Slider & Carousel Ultimate: from n/a through <= 1.6.10.

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

A Local File Inclusion (LFI) vulnerability in the wpWax Post Grid, Slider & Carousel Ultimate WordPress plugin (versions up to 1.6.10) allows attackers to include and execute arbitrary local PHP files due to improper control of filename parameters in include/require statements. This can lead to sensitive file disclosure and potentially remote code execution.

MitigationApply the latest plugin update immediately. Until patched, disable the plugin or implement web application firewall rules to block directory traversal patterns in HTTP requests. Audit for any signs of compromise.

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
Post Grid\, Slider \& Carousel UltimateWordPress extension
Affected:< 1.7

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 installation
    Locate the plugin in the WordPress wp-content/plugins directory. The plugin folder should be named 'post-grid-slider-carousel-ultimate' or similar. Check via WP admin dashboard under Plugins > Installed Plugins, or inspect the filesystem at /wp-content/plugins/
    Affected if The plugin is present in the WordPress installation
  2. Check installed version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Post Grid, Slider & Carousel Ultimate' to view the version number. Alternatively, read the main plugin PHP file (usually post-grid-slider-carousel-ultimate.php) and look for the 'Version' header in the plugin comment block
    Affected if The version is 1.6.10 or lower (anything less than 1.7)
  3. Identify vulnerable endpoint
    Locate the PHP file handling the include/require functionality. In affected versions, this is typically in the plugin's includes folder. Search for files containing 'include' or 'require' statements that use unsanitized variables like $_GET or $_POST for the filename parameter
    Affected if The plugin code contains include/require statements using uncontrolled input from HTTP request parameters
  4. Test for LFI exposure (if authorized)
    If you have authorization, send a crafted HTTP GET request to the vulnerable endpoint attempting directory traversal, such as ?file=../../../../wp-config.php. Check if the server returns file contents or PHP errors revealing the included file path
    Affected if The plugin accepts and processes directory traversal patterns in the file parameter without validation
  5. Audit access logs for exploitation attempts
    Review web server access logs (Apache/nginx) for requests to the plugin's PHP files containing patterns like '../', '..%2F', or references to wp-config.php, passwd, or other sensitive local files
    Affected if Log entries show directory traversal requests targeting the plugin endpoint

A WordPress site is affected if the Post Grid, Slider & Carousel Ultimate plugin is installed with version 1.6.10 or lower and the vulnerable include/require functionality is accessible.

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

Apply the latest plugin update immediately. Until patched, disable the plugin or implement web application firewall rules to block directory traversal patterns in HTTP requests. Audit for any signs of compromise.

Recommended fix Moderate confidence

version 1.7 or later

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate 'Post Grid, Slider & Carousel Ultimate' plugin
  4. Click 'Update Now' to upgrade to version 1.7 or later
  5. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running version 1.7 or higher in the Plugins list
  7. Test that the Post Grid/Carousel functionality works correctly on your site
Caveat WordPress plugin minor version upgrades typically have minimal breaking changes; test in staging if possible

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

Fix this in Post Grid\, Slider \& Carousel Ultimate Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
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,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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