| Plugin Name | WordPress Form Maker by 10Web |
|---|---|
| Type of Vulnerability | Cross Site Scripting |
| CVE Number | CVE-2026-1065 |
| Urgency | Medium |
| CVE Publish Date | 2026-02-08 |
| Source URL | CVE-2026-1065 |
Cross‑Site Scripting (CVE‑2026‑1065) in Form Maker by 10Web — What WordPress Site Owners Must Do Now
Unauthenticated stored XSS via SVG uploads in Form Maker (<=1.15.35) was published as CVE‑2026‑1065. This post explains the risk, how attackers can abuse SVG upload handling, how to detect exploitation, and a detailed mitigation and recovery checklist.
Why this vulnerability matters
Stored Cross‑Site Scripting (XSS) is a high‑impact client‑side vulnerability. In this case, unauthenticated attackers could upload crafted SVG files that persist on the site and execute JavaScript when rendered by visitors’ browsers. Because the vuln is unauthenticated, the attacker does not need a user account — only the ability to reach the vulnerable upload endpoint.
Potential consequences include:
- Theft of authenticated cookies and session tokens (leading to privilege escalation);
- Silent admin‑account takeover if administrators view infected pages;
- Persistent content injection (phishing, defacement, ad insertion);
- Drive‑by malware distribution to site visitors;
- Exfiltration of data accessible in a user’s browser (form entries, contact data);
- Reputational damage and SEO penalties.
SVGs are XML and may contain tags or event attributes such as onload. If upload handling only checks file extension or MIME type, malicious SVGs can bypass weak checks and run in your origin’s context.
Technical overview (non‑exploit)
Form Maker by 10Web versions up to and including 1.15.35 allow unauthenticated upload and storage of SVG files containing executable JavaScript. When those files are later served or embedded from your origin, the embedded script executes in the visitor’s browser. The issue is tracked as CVE‑2026‑1065 and has a CVSS v3.1 score of 7.1.
Why SVG is special
- SVGs are XML documents and can include script tags and event attributes (onload, onerror, etc.).
- Browsers render SVGs inline; inline JavaScript executes with the page’s origin.
- Some upload handlers only validate extension/MIME type and not actual content.
- A malicious SVG served from your domain can access cookies and the DOM for that origin.
We will not reproduce exploit code here. The guidance below focuses on safe detection, mitigation and recovery.
How attackers can abuse SVG uploads
High‑level attack flow
- Attacker locates an upload endpoint in Form Maker (or a form field) that accepts SVG files.
- They craft an SVG containing JavaScript or an event handler (for example, an
onloadattribute) that performs malicious actions when executed. - The crafted SVG is uploaded and stored on the site (commonly in
/wp-content/uploads/). - The attacker triggers visits to pages embedding or linking to that SVG, or waits for normal visitors/admins to load pages where the SVG is accessible.
- When a browser loads the SVG from your origin, the embedded script runs in that browser context with access to site cookies and DOM.
Common attacker objectives include cookie theft, content injection (phishing), admin takeover, pivoting to server‑side compromise, and data exfiltration.
Who is impacted
- Any WordPress site running Form Maker by 10Web at version 1.15.35 or earlier.
- Sites that allow uploaded SVGs to be served or rendered from the same origin.
- Administrators and site managers who might view infected pages.
- Visitors whose browsers may execute inline SVG scripts.
If you’re unsure which version you run, check Plugins > Installed Plugins in WP‑Admin or inspect wp-content/plugins/form-maker.
Detection: look for signs of exploitation
Perform these checks immediately — they help determine whether the vulnerability has been exploited.
1. Search uploads for recent SVGs
- Inspect
/wp-content/uploads/and other upload directories for.svgfiles added during the exposure window. - Look for unusual filenames or files uploaded by anonymous sources.