Image size ignores EXIF orientation, and the SVG sanitizer keeps external references
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Read src/plugins/FluentCMS.Plugins.Media/ImageSize.cs, MediaService.cs, SkiaImageProcessor.cs, and SvgDocument.cs, then review linked issue #3281 because it changes the same image processing. Trace how dimensions and SVG references are handled, and check the media tests. Done means EXIF-oriented dimensions are reported correctly, existing assets are backfilled, external SVG references and escaped @import are removed, and each behavior has a test.
由索引模型根据 Issue 内容生成。
描述
Problem
- Stored width and height ignore EXIF orientation. The size is read from the raw header (
src/plugins/FluentCMS.Plugins.Media/ImageSize.cs:65-122, used atMediaService.cs:927), while transforms swap for a turned image (SkiaImageProcessor.cs:41,99). A portrait phone JPEG reports its width and height swapped to API consumers. - The SVG sanitizer keeps external references. Remote
href/xlink:href,<use>,<image>andurl(https://…)are kept; onlyjavascript:,vbscript:and non-imagedata:are dropped (SvgDocument.cs:133-153).@importis removed by a string match (:155-159) that a CSS escape such as@\69mportpasses. The CSP sandbox covers a file served by the CMS (MediaEndpoints.cs:30,165-167), not an inlined SVG or a CDN that drops the header.
Proposal
- Take the size from
IImageProcessor.IdentifyAsync; backfill existing assets with a job. - Allow only same-document
#fragmentreferences, strip remoteurl(), and match@importafter unescaping.
Done together with #3281, which changes the same image processing.
Acceptance
- An image with a turned EXIF orientation reports the size it displays at
- Existing assets are corrected by the backfill
- A sanitized SVG contains no reference outside the document
- An escaped
@importis removed - Tests for each
Found in the code review of 17 Nov 2026.
- 主要语言
- C#
- 星标
- 569
- 派生
- 107
- 平均合并
- 2 小时 49 分钟
- 30 天内合并 PR
- 397
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
fluentcms/FluentCMS 的其他 Issue
-
area:host area:operations type:bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
area:build security type:chore
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
area:sdk security type:bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
area:content security type:bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
area:build type:bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
查看 fluentcms/FluentCMS 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 67/100
microsoft/microsoft-ui-reactor#1567 ·
维护者通常 1 天内回复
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
难度 2/5 1-3 小时 新手友好度 76/100
openclaw/openclaw-windows-node#2287 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
kind:ux needs-triage
难度 2/5 1-3 小时 新手友好度 66/100
elsa-workflows/elsa-foundation#4742 ·
维护者通常 1 天内回复
-
priority:P2
难度 2/5 1-3 小时 新手友好度 88/100