| 插件名稱 | 10Web 的 WordPress 表單製作器 |
|---|---|
| 漏洞類型 | 跨站腳本攻擊 |
| CVE 編號 | CVE-2026-1065 |
| 緊急程度 | 中等 |
| CVE 發布日期 | 2026-02-08 |
| 來源 URL | CVE-2026-1065 |
10Web 的表單製作器中的跨站腳本攻擊 (CVE‑2026‑1065) — WordPress 網站擁有者現在必須做什麼
透過 SVG 上傳的未經身份驗證的儲存 XSS 在表單製作器中 (<=1.15.35) 被發布為 CVE‑2026‑1065。這篇文章解釋了風險、攻擊者如何濫用 SVG 上傳處理、如何檢測利用,以及詳細的緩解和恢復檢查清單。.
為什麼這個漏洞很重要
儲存型跨站腳本攻擊(XSS)是一種高影響的客戶端漏洞。在這種情況下,未經身份驗證的攻擊者可以上傳精心製作的SVG文件,這些文件會持續存在於網站上,並在訪問者的瀏覽器中渲染時執行JavaScript。由於該漏洞不需要身份驗證,攻擊者不需要用戶帳戶——只需能夠訪問易受攻擊的上傳端點即可。.
潛在後果包括:
- 竊取經過身份驗證的 cookies 和會話令牌(導致特權提升);;
- 如果管理員查看受感染的頁面,則會靜默接管管理員帳戶;;
- 持久性內容注入(網絡釣魚、破壞、廣告插入);;
- 向網站訪客分發驅動式惡意軟件;;
- 從用戶的瀏覽器中提取可訪問的數據(表單條目、聯絡資料);;
- 名譽損害和 SEO 處罰。.
SVG 是 XML,可能包含 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.