DocumentationExperience Cloud KCS

Universal Editor component properties can’t be modified due to CORS configuration in AEMaaCS

Last update: October 28, 2026

Adobe Experience Manager as a Cloud Service (AEMaaCS) Universal Editor may display component content and properties but fail to apply changes when the CORS configuration blocks the requests required for editing. To resolve the issue, update the CORS configuration for the Universal Editor domain, required HTTP methods, and headers, deploy the changes, and verify component editing.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS), all versions

Issue/Symptoms

  • Pages load successfully in the Universal Editor, and component information is retrieved as expected.
  • Components display correctly, including their existing content and properties.
  • Changes to component data, such as properties or content, can’t be applied.
  • No explicit error message appears in the UI, but content authors can’t make changes through the Universal Editor.
  • The issue is reproducible by loading a page in the Universal Editor and attempting to edit a component.
  • Content authors can’t use the Universal Editor for content authoring and component editing.

Steps to reproduce:

  1. Load a page in the Universal Editor.
  2. Attempt to edit any component.
  3. Observe that changes to the component properties can’t be applied.

Root cause

An incorrect or incomplete CORS (Cross-Origin Resource Sharing) configuration blocks the Universal Editor from making the requests required to modify component data.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review the CORS (Cross-Origin Resource Sharing) configuration for the AEM environment.
  2. Ensure that the domain used by the Universal Editor, for example, experience.adobe.com, is included in the allowed origins for CORS requests in the AEM Publish and Author environments.
  3. Update the CORS configuration to allow the required HTTP methods, such as GET, POST, PUT, and OPTIONS, and the headers required by the Universal Editor.
  4. Save and deploy the updated CORS configuration.
  5. Clear the browser cache and reload the Universal Editor.
  6. Test component property editing again and confirm that the changes can be applied successfully.
recommendation-more-help
experience-cloud-kcs-help-kbarticles