Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

PostMessage origin validation flaw leading to stored XSS in Foxit webplugins embedded calculator

IdentifiersCVE-2025-66500CWE-346

A stored cross-site scripting vulnerability exists in webplugins.foxit.com within an embedded calculator component’s window.postMessage handler. The handler performs origin validation incorrectly by checking an attacker-controlled field (t.data.origin) rather than the browser-enforced event.origin. It then uses attacker-supplied data to set an externalPath value that is directly assigned as the source of a loaded script, enabling injection of a remote <script> into a trusted Foxit domain context when a crafted postMessage is received.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary JavaScript execution in the context of the trusted webplugins.foxit.com origin. This can enable session/token theft, account takeover workflows, and other same-origin impacts against users interacting with the affected Foxit web plugin content.

Mitigation

If you can’t patch tonight, do this now.

Deploy/strengthen CSP on webplugins.foxit.com to restrict script-src to trusted, non-user-controllable origins and disallow unsafe dynamic script loading where possible. As a defense-in-depth measure, add runtime message schema validation and logging/alerting for unexpected postMessage traffic patterns targeting the calculator component.

Remediation

Patch, then assume compromise.

Fix the postMessage handler to validate the sender using event.origin (and optionally event.source) against a strict allowlist, and reject messages that do not match expected origins and schemas. Additionally, prevent script-source assignment from untrusted message data (e.g., remove dynamic script injection or enforce a hardcoded/allowlisted set of script URLs).
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Foxit SoftwarePdf Editor Cloudapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.