Categories
CVE-2025-13159 high CVSS 7.1

Cross-Site Scripting (XSS) in WordPress (CVE-2025-13159)

Summary

Cross-site scripting in WordPress (CVE-2025-13159). Risk of unauthorized operations or information disclosure. Exploitable via flo_form_submit.

Original description

The description as published by the source.

The Flo Forms – Easy Drag & Drop Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG file uploads in all versions up to, and including, 1.0.43. This is due to the plugin allowing SVG file uploads via an unauthenticated AJAX endpoint (flo_form_submit) without proper file content validation. This makes it possible for unauthenticated attackers to upload malicious SVG files containing JavaScript that executes when an administrator views the uploaded file in the WordPress admin interface, leading to potential full site compromise.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-13159 has been found in WordPress.
Attackers can target a specific entry point like flo_form_submit over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress CVE-2025-13159" on the vendor's site.

CVE-2025-13159 (WordPress) — CWE-79 / CVSS v3 7.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: flo_form_submit
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in WordPress. Attackers reach the vulnerable code path via flo_form_submit without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of WordPress. Attack surface: flo_form_submit.

🔥 Severity

Severity: High (CVSS 7.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで WordPress を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details