Security readout for executives and security teams
Plain-English summary
Frog CMS 0.9.5 has a reflected XSS flaw in the admin file manager rename flow. A malicious request could run attacker-controlled script in a user's browser. The source says it can be combined with CSRF, so the main business risk is abuse of CMS administration activity if an admin is tricked.
Executive priority
Treat as a targeted legacy CMS risk, not a broad internet emergency. Prioritize if Frog CMS 0.9.5 manages public content, has exposed administration, or is used by privileged staff.
Technical view
CVE-2018-10806 describes reflected XSS through the file[current_name] parameter to the admin/?/plugin/file_manager/rename URI in Frog CMS 0.9.5. The record notes possible CSRF chaining. The provided sources do not include CVSS, CWE mapping, CPEs, exploit maturity, or a confirmed fixed version.
Likely exposure
Exposure is likely limited to organizations still running Frog CMS 0.9.5, especially where the admin interface is reachable by users or the internet. Evidence does not identify other affected versions.
Exploitation context
The CVE is not listed in KEV, and the provided sources do not show active exploitation. Practical risk depends on whether an attacker can induce a CMS administrator to visit or submit a malicious request.
Researcher notes
The public record is sparse. The affected product is named in the description, but structured affected metadata is absent. Avoid assuming patch availability, affected version ranges, or exploitation in the wild without additional vendor or repository evidence.
Mitigation direction
- Check vendor or project guidance for a fixed Frog CMS release.
- Restrict admin interface access to trusted networks or VPN.
- Require CSRF protections for admin state-changing actions.
- Review output encoding around file manager rename responses.
- Retire or replace unsupported Frog CMS deployments.
Validation and detection
- Inventory web assets for Frog CMS 0.9.5 installations.
- Confirm whether admin/?/plugin/file_manager/rename exists.
- Review source code for file[current_name] reflection and encoding.
- Check whether admin actions enforce CSRF tokens.
- Verify admin interfaces are not publicly exposed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-10806 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/philippe/FrogCMS/issues/10CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.