CVE-2025-68977
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-68977 is a DOM-Based Cross-Site Scripting (XSS) vulnerability in the DesignThemes Portfolio Addon plugin for WordPress. It affects all versions of the plugin up to and including version 1.5, with no official patch available as of the disclosure date. The vulnerability was reported by researcher Phat RiO on November 17, 2025, and published by Patchstack on December 17, 2025. It carries a CVSS v3.1 base score of 6.5 (Medium) (Patchstack).

Technical details

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-Site Scripting), specifically manifesting as DOM-Based XSS. This type of XSS occurs when client-side JavaScript dynamically writes attacker-controlled data to the DOM without proper sanitization or encoding, allowing malicious scripts to execute in the victim's browser context. Exploitation requires the attacker to have at least Contributor-level privileges on the WordPress site, and successful execution also requires a privileged user to interact with a crafted page or link (user interaction required). The attack vector is network-based with low complexity (Patchstack).

Impact

Successful exploitation allows an attacker to inject and execute malicious JavaScript in the browsers of users visiting the affected WordPress site, potentially leading to session hijacking, credential theft, unauthorized actions performed on behalf of victims, and defacement via injected redirects or advertisements. The scope is changed (C:L/I:L/A:L), meaning the impact extends beyond the vulnerable component to affect other resources in the browser context. While the individual impact per metric is rated Low, the combination across confidentiality, integrity, and availability represents a meaningful risk to site visitors and administrators (Patchstack).

Exploitability

No public proof-of-concept exploit code or evidence of active in-the-wild exploitation has been reported for CVE-2025-68977. The EPSS score is approximately 0.029% (0.000290), 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, noting it is unlikely to be exploited, though XSS vulnerabilities of this class are sometimes leveraged in mass-exploit campaigns targeting WordPress plugins (Patchstack).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the DesignThemes Portfolio Addon plugin version 1.5 or earlier using tools like WPScan or Shodan with WordPress-specific fingerprinting.
  2. Obtain Contributor Access: Gain at least Contributor-level access to the target WordPress site (e.g., via credential stuffing, phishing, or registration if open).
  3. Craft Malicious Payload: Create a post or portfolio entry containing a DOM-Based XSS payload that exploits the plugin's unsanitized JavaScript DOM manipulation (e.g., injecting <script> tags or event handlers into plugin-rendered fields).
  4. Deliver to Victim: Trick a privileged user (e.g., Administrator or Editor) into visiting the crafted page or clicking a malicious link that triggers the DOM-based script execution.
  5. Execute Malicious Script: The victim's browser executes the injected JavaScript, enabling session cookie theft, credential harvesting, or unauthorized administrative actions on the WordPress site (Patchstack).

Indicators of compromise

  • Logs: WordPress access logs showing unusual POST or GET requests to pages rendering the DesignThemes Portfolio Addon with encoded JavaScript payloads (e.g., %3Cscript%3E, javascript:, onerror=) in parameters.
  • File System: Unexpected modifications to plugin files in wp-content/plugins/designthemes-portfolio-addon/ or newly created PHP/JS files in the plugin directory.
  • Network: Outbound requests from the victim's browser to unknown external domains following interaction with portfolio pages (indicative of data exfiltration via XSS).
  • Logs: WordPress audit logs (if enabled) showing Contributor-level users creating or editing portfolio entries with suspicious HTML or script content.

Mitigation and workarounds

As of the disclosure date, no official patched version of the DesignThemes Portfolio Addon plugin is available. Site administrators should consider deactivating and removing the plugin until a patch is released by the vendor. As a compensating control, restrict Contributor-level user registration and permissions, and implement a Web Application Firewall (WAF) with XSS filtering rules — Patchstack's virtual patching feature can provide protection for subscribers. Regularly audit user accounts with Contributor or higher privileges to minimize the attack surface (Patchstack).

Community reactions

The vulnerability was included in Wordfence's weekly WordPress vulnerability report covering December 15, 2025 to January 4, 2026, indicating routine tracking by the WordPress security community. No significant vendor statements, researcher commentary, or broader media coverage has been identified beyond standard vulnerability database listings (Wordfence Blog).

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-77115HIGH7.1
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-77116MEDIUM4.3
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-14853MEDIUM4.3
  • woocommerce-bookings
NoYesAug 23, 2026
CVE-2026-77003LOW2.7
  • content-mask
NoYesAug 23, 2026
CVE-2026-13598NONEN/A
  • restrictmate
NoYesAug 23, 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