Security: Update Next.js example to React 19.2.1+ to address CVE in React Server Components
Open
@rsh1k is already working on this.
Since Apr 1, 2026.
dotCMS : SDK
OKR : Security & Privacy
Priority : 4 Low
stale
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Vulnerability Summary
React has disclosed a critical security vulnerability (CVSS 10.0) in React Server Components affecting React versions 19.0, 19.1.0, 19.1.1, and 19.2.0. While dotCMS core is not affected, our Next.js example application uses React 19.1.0 and should be updated as a precautionary measure.
Impact Assessment
dotCMS Core: NOT AFFECTED ✅
- Main application uses React 18.3.1
- No vulnerable packages (
react-server-dom-webpack,react-server-dom-parcel,react-server-dom-turbopack) found - No React Server Components in core product
Next.js Example: POTENTIALLY AFFECTED ⚠️
- Location:
examples/nextjs/ - Current version: React 19.1.0 + Next.js 15.3.2
- Status: Example/demo application, not part of core product
- Risk: Low (example code, not production)
Vulnerability Details
- CVE: React Server Components Remote Code Execution
- CVSS Score: 10.0 (Critical)
- Affected Versions: React 19.0, 19.1.0, 19.1.1, 19.2.0
- Fixed Versions: React 19.0.1, 19.1.2, 19.2.1+
- Attack Vector: Malicious HTTP requests to Server Function endpoints
- Affected Packages:
react-server-dom-webpackreact-server-dom-parcelreact-server-dom-turbopack
Recommended Action
Update the Next.js example to use React 19.2.1 or later:
cd examples/nextjs
npm install react@19.2.1 react-dom@19.2.1
Update examples/nextjs/package.json:
{
"dependencies": {
"react": "19.2.1",
"react-dom": "19.2.1"
}
}
Verification Steps
- Update dependencies in
examples/nextjs/package.json - Run
npm installto update lock file - Test the example application:
cd examples/nextjs npm run dev npm run build - Verify no functionality regressions
Additional Context
- This is a precautionary update for example code
- Core dotCMS product is not affected and requires no action
- Next.js example does not explicitly install vulnerable packages, but updating ensures protection
- Next.js 15.3.2 may transitively depend on affected packages
References
- React Security Advisory: https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
- CVSS Calculator: https://www.first.org/cvss/calculator/4.0#CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Priority
Medium - Example code only, not production code, but should be updated for best practices
Generated with Claude Code
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.