-
Notifications
You must be signed in to change notification settings - Fork 2
RichText component returns 403 error after upgrading from v13 to v15 #707
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @richardinitial , does it only fail for old content or it fails even if you re-enter the links from the new RTE? |
Hi @umbracotrd it happens for both scenarios. |
thank you for confirming @richardinitial . After checking I see that the Can you try replicating the issue on a simple page type which contains only one rich text editor property? If you can then I suggest you forward this issue to Umbraco CMS repository to get appropriated support. |
Update: I ran the test you recommended, and only when I create a new page and add the component with the content am I able to save it successfully. But after saving it the first time, when I make any changes and try to save again, the error occurs. I'll forward this to the Umbraco CMS team. Thank you! |
I'm glad you can reliably reproduce the issue—identifying it is half the battle 💪. |
Which component is this issue related to?
Umbraco Commerce (Core)
Which Umbraco Commerce version are you using? (Please write the exact version, example: 10.1.0)
15.3.4
Bug summary
After migrating our project from Umbraco 13 to 15, we noticed that pages containing RichText components (specifically of type Umb.PropertyEditorUi.TinyMCE | Umbraco.RichText) started throwing an API error when trying to save changes.
Upon inspecting the network requests, the error occurs on the Validate request, which includes an HTML payload generated by the RichText editor. The server responds with 403 Forbidden.
Specifics
Curiously, when debugging the code, the same request completes successfully with a 200 OK status.
We also tested with a TipTap RichText editor, but the issue persists.
Note:
This issue only started after the upgrade to v15.
During debugging sessions, the validation completes successfully, suggesting it could be a security or permission-related check introduced or modified in v15.
Error message

Payload info

Console Log Errors

User Permissions

Example HTML markup triggering the error:
If I remove these 2 elements it works fine

Steps to reproduce
Saving a page with RichText content triggers a 403 error from the Validate endpoint.
If the RichText field is emptied, saving succeeds.
Expected result / actual result
No response
Dependencies
No response
The text was updated successfully, but these errors were encountered: