Security readout for executives and security teams
Plain-English summary
Ubiquiti UCRM 2.5.0 through 2.7.7 can store attacker-supplied HTML through an uploaded filename. The attacker needs valid credentials with Scheduling Edit access, so this is not an unauthenticated internet takeover. Business risk is account abuse, phishing, session theft, or misleading content shown to staff using UCRM.
Executive priority
Treat this as a targeted business-application risk rather than an emergency internet-wide exposure. Prioritize version confirmation, privilege reduction, and vendor-guided upgrade planning, especially where UCRM supports billing, scheduling, or customer operations.
Technical view
The issue is stored cross-site scripting caused by insufficient filename sanitization during upload handling. Malicious HTML in an uploaded filename can be persisted and later rendered in UCRM. The CVE states exploitation requires an authenticated account with Edit access to Scheduling. No CVSS vector, CWE, patch version, or affected CPE data is provided in the bundle.
Likely exposure
Exposure is limited to UCRM deployments on versions 2.5.0 to 2.7.7 where users can upload scheduling-related files. Risk increases if many internal or customer accounts have Scheduling Edit permission, or if UCRM is reachable from untrusted networks.
Exploitation context
The source bundle does not show active exploitation, public exploit use, or KEV listing. Exploitation requires valid credentials and specific application permission, but stored XSS can affect later viewers once the malicious filename is saved.
Researcher notes
Key evidence gaps are severity scoring, CWE assignment, patch version, exploit telemetry, and detailed sink location. Analysis should stay bounded to the CVE statement: stored XSS through uploaded filename manipulation requiring authenticated Scheduling Edit access.
Mitigation direction
- Inventory UCRM instances and confirm whether versions 2.5.0 through 2.7.7 are present.
- Check Ubiquiti release notes and support guidance for the corrected upgrade path.
- Restrict Scheduling Edit access to users who operationally require it.
- Review uploaded filenames and scheduling attachments for unexpected HTML-like content.
- Limit UCRM access to trusted networks where feasible.
Validation and detection
- Confirm exact UCRM version from application administration or deployment records.
- Review account roles for users with Scheduling Edit permission.
- Inspect recent scheduling uploads for suspicious filenames without opening untrusted content in browsers.
- Check vendor guidance for whether later UCRM releases address this CVE.
- Verify logs for unusual scheduling upload activity by privileged users.
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-0912 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://community.ubnt.com/t5/UCRM/New-UCRM-upgrades-available-2-8-2-and-2-9-0-beta3/td-p/2211814CVE 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.