Loading vulnerability…
CVE-2025-23922 is a Cross-Site Request Forgery (CSRF) vulnerability affecting Harsh iSpring Embedder through version 1.0. According to the provided description, the flaw allows an attacker to induce a privileged user of the application to submit a forged request that results in uploading a web shell to the web server. This indicates insufficient verification of request origin or anti-CSRF protections on functionality related to file upload or plugin content management. Successful exploitation can turn a browser-based request forgery into arbitrary server-side file placement of attacker-controlled content.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2025-23922, a critical CSRF vulnerability in the WordPress iSpring Embedder plugin (versions 1.0 and below). The exploit is delivered as an HTML file containing a form that, when visited by an authenticated WordPress administrator, will submit a ZIP file to the vulnerable plugin endpoint without CSRF protection. The uploaded ZIP is extracted to '/wp-content/uploads/iSpring_embedder/', allowing an attacker to upload arbitrary files, such as a PHP web shell, and potentially achieve remote code execution. The repository contains only a README.md (with the PoC HTML code and detailed vulnerability description) and a LICENSE file. No additional scripts or automation are provided.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.