Skip to main content
Vulnerability Database/CVE-2025-12151

CVE-2025-12151: WordPress Simple Folio XSS Vulnerability

CVE-2025-12151 is a stored XSS vulnerability in the WordPress Simple Folio plugin that lets authenticated attackers inject malicious scripts via the portfolio_name parameter. This article covers technical details, affected versions, impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-12151 Overview

The Simple Folio plugin for WordPress contains a Stored Cross-Site Scripting (XSS) vulnerability in the portfolio_name parameter. The flaw affects all versions up to and including 1.1.0. Insufficient input sanitization and output escaping allow authenticated attackers with Subscriber-level access or higher to inject arbitrary web scripts. The injected scripts execute whenever a user accesses the affected page. The issue is tracked as [CWE-79] and was published to the National Vulnerability Database (NVD) on November 27, 2025.

Critical Impact

Authenticated attackers with low-privilege Subscriber accounts can inject persistent JavaScript that executes in the browsers of site visitors and administrators, enabling session theft, forced redirects, and administrative action hijacking.

Affected Products

  • Simple Folio plugin for WordPress — all versions through 1.1.0
  • WordPress sites with the plugin active and user registration enabled
  • Any site allowing Subscriber-level accounts or higher with access to portfolio creation

Discovery Timeline

  • 2025-11-27 - CVE-2025-12151 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-12151

Vulnerability Analysis

The vulnerability is a Stored Cross-Site Scripting (XSS) issue classified under [CWE-79]. The Simple Folio plugin accepts user-supplied input through the portfolio_name parameter without applying proper sanitization on write or escaping on render. Attacker-controlled markup, including <script> tags and event handlers, persists in the WordPress database. When any user — including administrators — loads a page that renders the stored portfolio name, the injected JavaScript executes under the site origin.

Because the vulnerability requires only Subscriber-level privileges, the attack surface includes any WordPress site that permits open user registration. The scope-change rating indicates the executed script can affect resources beyond the vulnerable component, such as the administrator session context.

Root Cause

The plugin fails to call WordPress sanitization functions such as sanitize_text_field() on input and omits escaping functions such as esc_html() or esc_attr() on output. Portfolio data is written to and retrieved from the database with HTML metacharacters intact, allowing stored script payloads to render as executable markup in the browser.

Attack Vector

An attacker registers a Subscriber account on a vulnerable WordPress site. The attacker submits a crafted portfolio_name value containing JavaScript, for example an <img> tag with an onerror handler or a <script> block. The payload is stored in the wp_posts or associated metadata tables. When an administrator or visitor navigates to a page that displays the portfolio entry, the browser parses the injected markup and executes the script in the context of the WordPress domain. Common post-exploitation actions include stealing authentication cookies, performing CSRF against admin endpoints, and creating new administrator accounts.

No verified public proof-of-concept code is available at this time. Refer to the Wordfence Vulnerability Report for additional technical context.

Detection Methods for CVE-2025-12151

Indicators of Compromise

  • Portfolio entries containing <script>, onerror=, onload=, or javascript: strings in the portfolio_name field
  • Unexpected creation of new administrator accounts following Subscriber account activity
  • Outbound requests from visitor browsers to unknown third-party domains sourced from WordPress pages
  • New Subscriber registrations followed shortly by portfolio creation activity on the /wp-admin/post-new.php endpoint

Detection Strategies

  • Query the WordPress database for portfolio records where the name field contains HTML tags or JavaScript event handlers
  • Review web server access logs for POST requests to Simple Folio endpoints originating from low-privilege accounts
  • Monitor the browser Content Security Policy (CSP) violation reports for inline script execution on portfolio pages
  • Scan rendered HTML output of portfolio pages for unexpected <script> tags using automated crawlers

Monitoring Recommendations

  • Enable WordPress audit logging for user registration, role changes, and post creation events
  • Alert on administrator account creation events that occur outside of change-management windows
  • Track plugin version inventory across managed WordPress deployments to confirm patch status
  • Correlate Subscriber login activity with subsequent content submission to identify abuse patterns

How to Mitigate CVE-2025-12151

Immediate Actions Required

  • Update the Simple Folio plugin to a version later than 1.1.0 once released by the maintainer
  • Disable or remove the Simple Folio plugin if a patched version is not yet available
  • Review existing portfolio entries for malicious payloads and delete affected records
  • Audit WordPress user accounts for unauthorized Subscriber or Administrator registrations

Patch Information

Review the WordPress Plugin Changeset for the vendor fix applied to the Simple Folio plugin. Confirm that the deployed version includes proper calls to sanitize_text_field() on input and esc_html() on output of the portfolio_name field. Administrators should subscribe to the Wordfence Vulnerability Report for updates on fixed version availability.

Workarounds

  • Disable open user registration under Settings → General by unchecking "Anyone can register" until patched
  • Deploy a Web Application Firewall (WAF) rule to block requests containing script tags in the portfolio_name parameter
  • Restrict access to portfolio creation endpoints via server-level ACLs to trusted IP ranges
  • Set a strict Content Security Policy (CSP) header that disallows inline scripts on portfolio-rendering pages
bash
# Example WordPress hardening via wp-config.php and .htaccess
# Disable user registration programmatically
update_option('users_can_register', 0);

# Example Apache rule to block script injection in portfolio_name
RewriteEngine On
RewriteCond %{QUERY_STRING} portfolio_name=.*(<|%3C)script [NC]
RewriteRule .* - [F,L]

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.