wp

[mokimo]

• Add your
• Specific
• Features or fixes

Resolves: MWPW-NUMBER

Test URLs:

• Before: https://main--milo--adobecom.aem.page/?martech=off
• After: https://--milo--adobecom.aem.page/?martech=off

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run PSI checks
• Re-sync branch

Commits

• 95d3ce2 ✅ (latest)
• c58ef7d ✅
• 2d5b5bf ✅
• 746f58e ✅
• be5c164 ✅
• ef0d2ce ✅
• 1ce78a0 ✅
• e01e1bf ✅
• 239f08a ✅
• b6e2bcd ✅
• c582faa ✅
• 5bbb0bf ✅
• 06c149b ✅
• 56b944a ✅
• a8222fd ✅
• 5ed9985 ✅
• dd15662 ✅
• 0c20425 ✅
• 73cb4e7 ✅
• bfe9f9b ✅
• faf70c2 ✅
• 82694a3 ✅
• b063e5d ✅
• e7fc894 ✅
• d53dab7 ✅
• e4f9999 ✅
• 238caed ✅
• ea9f4a9 ✅
• 7db0ff0 ✅
• d389752 ✅

To fix the problem, we need to ensure that the modalType variable is properly sanitized before being used in the innerHTML assignment. This can be achieved by using a function that escapes any potentially dangerous characters in the modalType string. We can use a well-known library like DOMPurify to sanitize the input.

1. Import the DOMPurify library.
2. Use DOMPurify.sanitize to sanitize the modalType variable before using it in the innerHTML assignment.

To fix the problem, we need to ensure that the text content is properly escaped before being inserted into the HTML. This can be achieved by creating a text node and appending it to the container, which ensures that any special characters are properly escaped.

• Replace the direct insertion of el.textContent into the HTML with a method that safely escapes the text content.
• Specifically, create a text node for the content and append it to the container.

To fix the problem, we need to ensure that any text content inserted into the DOM is properly escaped to prevent XSS attacks. This can be achieved by using a text node instead of setting innerHTML directly. By creating a text node, we ensure that any special characters in the text content are properly escaped.

• Replace the use of innerHTML with a method that safely inserts text content.
• Specifically, create a text node for the text content and append it to the target container.

To fix the problem, we need to ensure that the innerHTML parameter is sanitized before being inserted into the DOM. This can be achieved by using a library like DOMPurify to sanitize the input. This approach will allow us to maintain the existing functionality while ensuring that any potentially unsafe HTML is cleaned before being used.

To fix the problem, we need to escape the . meta-character in the regular expression to ensure that it matches only the literal . character. This will prevent unintended matches and ensure that the regular expression only matches the intended domain.

• Locate the regular expression on line 157 in the file libs/features/mas/test/mas-commerce-service.test.js.
• Modify the regular expression to escape the . character before adobe.com.