Security readout for executives and security teams
Plain-English summary
October CMS build 412 has a reported weakness in asset move handling that can let file paths be modified, resulting in malicious files being created on the server. The public record is sparse, with no CVSS score, CWE, or detailed affected-product metadata provided.
Executive priority
Treat this as a targeted platform hygiene issue unless your organization runs October CMS build 412. If present on internet-facing or business-critical sites, prioritize upgrade review and file integrity checks because server-side malicious file creation can become operationally serious.
Technical view
The CVE describes file path modification in October CMS build 412 asset move functionality, leading to malicious file creation on the server. The only technical reference supplied is the October CMS comparison from v1.0.412 to v1.0.413. No exploit details, CVSS vector, CWE, or affected CPEs are provided.
Likely exposure
Likely exposure is limited to environments running October CMS build 412 where the asset move functionality is available. The provided CVE metadata does not identify CPEs, hosting patterns, required privileges, or whether unauthenticated access is possible.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. It also does not include proof-of-concept status, exploit maturity, or attacker prerequisites.
Researcher notes
Evidence is incomplete. The record names October CMS build 412 and a file path modification issue, but omits CVSS, CWE, prerequisites, and affected CPEs. Avoid assuming remote unauthenticated exploitation. Use the v1.0.412-to-v1.0.413 comparison and local code/version checks to confirm exposure.
Mitigation direction
- Inventory October CMS installations and identify build 412 instances.
- Review October CMS vendor guidance and the v1.0.413 comparison reference.
- Plan upgrade away from build 412 after compatibility testing.
- Restrict access to asset management functions to trusted administrators.
- Monitor web roots and writable directories for unexpected files.
Validation and detection
- Confirm the deployed October CMS build number on each instance.
- Check whether asset move functionality is enabled and reachable.
- Review server files for unexpected recently created assets or scripts.
- Review application and web server logs around asset move activity.
- Validate remediation in staging before production rollout.
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-1000197 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/octobercms/october/compare/v1.0.412...v1.0.413#diff-eef90a4e3585febf6489916dc242d0ceR241CVE 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.