Categories
CVE-2025-14804 high CVSS 7.7

Vulnerability in Frontend File Manager Plugin (WordPress plugin) (CVE-2025-14804)

Summary

Vulnerability in Frontend File Manager Plugin (WordPress plugin) (CVE-2025-14804). Data can be tampered with by attackers.

Original description

The description as published by the source.

The Frontend File Manager Plugin WordPress plugin before 23.5 did not validate a path parameter and ownership of the file, allowing any authenticated users, such as subscribers to delete arbitrary files on the server

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-14804 has been found in Frontend File Manager Plugin (WordPress plugin).
Data can be tampered with by attackers. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Frontend File Manager Plugin (WordPress plugin) CVE-2025-14804" on the vendor's site.

CVE-2025-14804 (Frontend File Manager Plugin (WordPress plugin)) — CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
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

A vulnerability (unclassified) exists in Frontend File Manager Plugin (WordPress plugin).

📍 Affected scope

Check the vendor advisory for the affected versions of Frontend File Manager Plugin (WordPress plugin).

🔥 Severity

Severity: High (CVSS 7.7/10). Data can be tampered with by attackers.

🔧 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・依存マニフェストで Frontend File Manager Plugin (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  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