← 输入框|github.com|刷新
Skip to content

[GHSA-fc9r-7hhq-7wqj] Add affected package EPiServer.CMS.UI < 12.32.0 (CVE-2025-22389) - #10692

Open
larsflagan wants to merge 4 commits into
github:larsflagan/advisory-improvement-10692from
larsflagan:larsflagan/advisory-improvement-GHSA-fc9r-7hhq-7wqj
Open

larsflagan wants to merge 4 commits into
github:larsflagan/advisory-improvement-10692from
larsflagan:larsflagan/advisory-improvement-GHSA-fc9r-7hhq-7wqj

Conversation

@larsflagan

@larsflagan larsflagan commented Oct 26, 2026 •

Copy link
Copy Markdown

Updates

  • Affected products
  • References

Optimizely security advisory: CMS-2025-03 (CVE-2025-22389)

Comments
CVE-2025-22389 has no affected package, so Dependabot and dotnet list package --vulnerable don't report it to anyone using the vulnerable versions.

Optimizely's advisory (https://support.optimizely.com/hc/en-us/articles/33182404079629-Content-Management-System-CMS-Security-Advisory-CMS-2025-03) names the affected package and the fix:

Affected: EPiServer.CMS.UI versions before 12.32.0
Remediation: Upgrade to EPiServer.CMS.UI version 12.32.0

This PR:

The current details text comes from NVD and says "EPiServer.CMS.Core before 12.32.0". That doesn't match the vendor advisory: EPiServer.CMS.Core has no 12.32.x release (its latest 12.x is 12.24.3), so the affected package is EPiServer.CMS.UI.

🤖 Generated with Claude Code

Copilot AI max review requested due to automatic review settings October 26, 2026 22:27

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The vendor-hosted NuGet package needs curator confirmation against the repository’s documented nuget.org registry scope.

1 open issue
What changed in this PR

This PR adds affected-package metadata for CVE-2025-22389 to the advisory database, linking the vulnerability to the CMS UI package identified in the quoted vendor guidance.

Changes:

  • Adds EPiServer.CMS.UI in the NuGet ecosystem.
  • Marks versions before 12.32.0 as affected and records 12.32.0 as fixed.
File Description
advisories/​unreviewed/​2025/​01/​GHSA-fc9r-7hhq-7wqj/​GHSA-fc9r-7hhq-7wqj.json Adds the affected NuGet package and fixed-version boundary.

Review effort: Max

{
"package": {
"ecosystem": "NuGet",
"name": "EPiServer.CMS.UI"

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed: details now says EPiServer.CMS.UI before 12.32.0, matching the affected entry and the vendor advisory.

@github-actions
github-actions Bot changed the base branch from main to larsflagan/advisory-improvement-10692 October 26, 2026 22:38
@larsflagan

Copy link
Copy Markdown
Author

Thanks. Correct, EPiServer.CMS.UI isn't on nuget.org. It's only published on Optimizely's public NuGet feed (https://nuget.optimizely.com/feed/packages.svc/), which .NET projects add as a package source. The package ID is the same one used in PackageReference, so scanners match it by name.

I understand this may be outside the supported NuGet scope. If so, could the curators still accept the corrected details text (EPiServer.CMS.UI instead of EPiServer.CMS.Core) and the ADVISORY reference type? I'm happy to drop the affected entry if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants