The Frontend File Manager & Sharing WordPress plugin before 1.1.3 does not filter file extensions when letting users upload files on the server, which may lead to malicious code being uploaded.
Security readout for executives and security teams
Plain-English summary
A WordPress file-management plugin reportedly allowed unsafe file uploads before version 1.1.3. If exposed on a site, an attacker could upload dangerous files that may affect site confidentiality or integrity. The source bundle does not show confirmed active exploitation, but the vulnerability is easy to reach under the listed CVSS assumptions.
Executive priority
Prioritize remediation for public WordPress sites and sites allowing user uploads. The issue is not KEV-listed in the bundle, but unrestricted upload flaws can create direct business impact if abused.
Technical view
CVE-2022-2356 is a CWE-434 unrestricted file upload issue in Frontend File Manager & Sharing, also named User Private Files. The plugin did not filter uploaded file extensions before 1.1.3, allowing malicious code to be placed on the server. Source metadata conflicts on access requirements: title says Subscriber+, while CVSS lists PR:N.
Likely exposure
Exposure is most likely on WordPress sites using Frontend File Manager & Sharing / User Private Files before 1.1.3, especially where file upload features are available to public or subscriber-level users. Verify exact installed versions because the bundle’s affected-version field conflicts with the title and description.
Exploitation context
The bundle includes a WPScan reference tagged as exploit, but it does not provide KEV listing or evidence of active in-the-wild exploitation. Treat internet-facing WordPress upload functionality as a practical risk, while avoiding assumptions beyond the cited sources.
Researcher notes
Key uncertainty is access control: the title indicates Subscriber+, while CVSS says no privileges required. Validate from the deployed plugin behavior and vendor advisory before assigning exposure scope. Do not assume active exploitation from the provided evidence.
Mitigation direction
Confirm vendor guidance for the fixed version and update accordingly.
Disable or remove the plugin if a safe version cannot be verified.
Restrict upload access to trusted users only.
Block execution from upload directories using hosting or web-server controls.
Review uploaded files for unexpected executable content.
Validation and detection
Inventory WordPress sites for the affected plugin name and version.
Check whether user registration or subscriber-level uploads are enabled.
Review upload directories for recently added suspicious file types.
Confirm file-extension filtering is enforced after remediation.
Retest affected routes without using exploit payloads.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · medium confidence lookup
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.