CVE-2026-12385
Deferred Deferred - Pending Action

Sensitive Information Exposure in Smart Slider 3 WordPress Plugin

Vulnerability report for CVE-2026-12385, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-14

Assigner: Wordfence

Description

The Smart Slider 3 plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.5.1.37 via the 'keyword' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to extract titles and full content excerpts of private, draft, pending, trashed, and auto-draft posts authored by any user, including Administrators and Editors. The required nonce is emitted on /wp-admin/post-new.php, which is accessible to Contributor-level users via the edit_posts capability, meaning any Contributor can obtain the nonce needed to trigger the injection.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-14
Generated
2026-08-03
AI Q&A
2026-07-14
EPSS Evaluated
2026-08-01
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
smart_slider smart_slider_3 to 3.5.1.37 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-12385 is a vulnerability in the Smart Slider 3 plugin for WordPress. It involves Sensitive Information Exposure via the 'keyword' parameter. This flaw allows authenticated attackers with contributor-level access or higher to extract sensitive information from the WordPress site.

Specifically, attackers can obtain titles and full content excerpts of posts that are private, draft, pending, trashed, or auto-draft. This includes posts authored by any user, such as Administrators and Editors. The vulnerability is exploitable because the required nonce (a security token) is emitted on the /wp-admin/post-new.php page, which is accessible to Contributor-level users.

  • Affected versions: All versions of Smart Slider 3 up to and including 3.5.1.37.
  • Attacker requirements: Authenticated access with contributor-level permissions or higher.
  • Exposed data: Titles and content excerpts of private, draft, pending, trashed, and auto-draft posts.
Detection Guidance

Detecting this vulnerability requires checking for unauthorized exposure of sensitive post information via the Smart Slider 3 plugin in WordPress. Since the vulnerability involves the 'keyword' parameter, you can monitor network traffic or logs for requests to the plugin's endpoints that include this parameter.

  • Check WordPress access logs for requests to the Smart Slider 3 plugin endpoints, particularly those containing the 'keyword' parameter. Look for unusual or repeated requests from contributor-level users.
  • Use a web application firewall (WAF) or security plugin like WordFence to monitor and log requests to /wp-admin/post-new.php, as this is where the required nonce is emitted and accessible to contributor-level users.
  • Inspect the WordPress database for any unauthorized access or extraction of private, draft, pending, trashed, or auto-draft posts. This may require querying the wp_posts table for unusual activity.

Example command to search Apache/Nginx logs for requests involving the 'keyword' parameter:

  • grep 'keyword=' /var/log/apache2/access.log | grep 'smart-slider'
  • grep 'keyword=' /var/log/nginx/access.log | grep 'smart-slider'
Impact Analysis

If you are using the Smart Slider 3 plugin on your WordPress site, this vulnerability could have several impacts.

  • Unauthorized access to sensitive information: Attackers with contributor-level access can view private or unpublished post content, including drafts, trashed posts, or auto-drafts. This could expose confidential or unreleased information.
  • Privilege escalation risks: While the vulnerability itself does not grant higher privileges, the exposed information could be used to craft further attacks or gain insights into administrative or editorial activities.
  • Reputation damage: If sensitive or internal content is leaked, it could harm your organization's reputation or lead to unintended public disclosure of private information.
  • Compliance violations: Depending on the nature of the exposed data, this vulnerability could lead to violations of data protection regulations if the leaked content includes personal or sensitive data.
Compliance Impact

This vulnerability can have significant implications for compliance with various standards and regulations, depending on the type of data exposed.

  • GDPR (General Data Protection Regulation): If the exposed posts contain personal data of EU citizens, this vulnerability could lead to a breach of GDPR. Unauthorized access to such data may be considered a violation, especially if the data is sensitive (e.g., health information, financial details). Organizations may face fines or legal consequences if they fail to protect personal data adequately.
  • HIPAA (Health Insurance Portability and Accountability Act): If the WordPress site handles protected health information (PHI) and such data is exposed due to this vulnerability, it could result in a HIPAA violation. HIPAA requires strict safeguards for PHI, and unauthorized access could lead to penalties.
  • Other regulations: Depending on the industry, other regulations like PCI DSS (for payment data) or sector-specific laws may also be impacted if the exposed data includes regulated information. Compliance failures could result in legal, financial, or operational consequences.

Organizations should assess whether the exposed data falls under any regulatory requirements and take steps to mitigate the risk, such as updating the plugin or implementing additional access controls.

Mitigation Strategies

To mitigate this vulnerability, follow these immediate steps:

  • Update the Smart Slider 3 plugin to the latest version if a patch is available. The vulnerability affects versions up to and including 3.5.1.37.
  • Restrict contributor-level access to the /wp-admin/post-new.php page if it is not required for their role. This can be done using a plugin or custom code to modify capabilities.
  • Monitor and audit user roles and permissions in WordPress to ensure that only trusted users have contributor-level access or higher.
  • Enable logging and monitoring for unusual activity, such as repeated requests to the Smart Slider 3 plugin endpoints or attempts to access sensitive post information.
  • Consider using a security plugin like WordFence to block or alert on suspicious activity related to this vulnerability.
  • Review and remove any unnecessary or unused plugins to reduce the attack surface of your WordPress installation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-12385. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart