Security readout for executives and security teams
Plain-English summary
Wolf CMS 0.8.3.1 has a stored or reflected XSS risk in its file manager workflow. An attacker who can reach the affected admin file manager action may inject script through file or directory names. The sources do not provide CVSS, affected version range, or a named patched version.
Executive priority
Treat this as a targeted legacy CMS risk, not an internet-wide emergency based on current evidence. Prioritize if Wolf CMS 0.8.3.1 is still deployed, especially where admin access is broadly reachable or shared.
Technical view
The CVE describes insufficient sanitization of file names in create-file-popup and directory names in create-directory-popup, submitted by HTTP POST to /plugin/file_manager/ and associated /admin/plugin/file_manager/browse// paths. Public PoC reference exists, but the source bundle does not confirm active exploitation or remediation details.
Likely exposure
Exposure is most likely limited to sites running Wolf CMS 0.8.3.1 with the file_manager admin plugin reachable to untrusted or compromised users. The bundle does not prove other versions, forks, or products are affected.
Exploitation context
CISA KEV is false in the bundle, and no cited source confirms active exploitation. A public proof-of-concept reference exists, so defenders should assume the issue is known to researchers and potentially reproducible.
Researcher notes
The record lacks CVSS, CWE, concrete vendor fix data, and a reliable affected-version range beyond Wolf CMS 0.8.3.1. Focus validation on authenticated admin file manager exposure, input handling, and whether downstream forks changed sanitization behavior.
Mitigation direction
- Inventory any Wolf CMS 0.8.3.1 deployments and exposed admin file manager paths.
- Restrict admin and file manager access to trusted users and networks.
- Check Wolf CMS maintainer or fork guidance for a fixed release or patch.
- If maintaining the code, sanitize and output-encode file and directory names.
- Review CMS admin sessions and recent file manager activity for suspicious changes.
Validation and detection
- Confirm whether Wolf CMS 0.8.3.1 is present in production or staging.
- Check whether /admin/plugin/file_manager/ is reachable from untrusted networks.
- Review application code for sanitization around create-file-popup and create-directory-popup inputs.
- Verify logs for unusual file or directory creation attempts in the admin file manager.
- Do not run public PoC material against production systems.
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-2017-11611 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/faizzaidi/Wolfcms-v0.8.3.1-xss-POC-by-Provensec-llcCVE 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.