Blog posts by Phu Nguyen

Blog posts by Phu Nguyen2025-08-08T10:18:13.0000000Zhttps://world.optimizely.com/blogs/phu-nguyen/ Optimizely World Episerver.CMS 12.33.2 delisted from Nuget feedWe have recently delisted version 12.33.2 of the <a href="https://nuget.optimizely.com/packages/episerver.cms">Episerver.CMS</a> package due to a packaging issue that may cause compatibility problems in certain scenarios. The DLL version is 1.0.0 instead of 12.33.2. This issue only affects projects that have a direct dependency on the Episerver.CMS DLL, such as Commerce sites or any other library that depends directly on the Episerver.CMS DLL. If you’re already using CMS 12.33.2 and encounter problems, a possible workaround is to install Episerver.CMS.UI version 12.33.2 directly in your site instead of using Episerver.CMS. However, our recommendation is to either: <ul> <li> Revert to version 12.33.1, or </li> <li> Wait for version 12.33.3, which will contain a fix and will be released shortly. </li> </ul> We apologize for the inconvenience and appreciate your understanding. Update Aug-11: the package Episerver.CMS 12.33.3 is now available on our public feed <a href="https://nuget.optimizely.com/packages/episerver.cms/12.33.3">https://nuget.optimizely.com/packages/episerver.cms/12.33.3</a>2025-08-08T10:18:13.0000000Z

Blog post

Vulnerability in EPiServer.FormsIntroduction We recently fixed a potential security vulnerability for the Optimizely Forms addon, customers may face this issue with any Forms version, the problem will happen when using a CMS function without noticing its noted behaviors. It could lead to losing security protection for some of the end-users' data. Risk Overall, the risk of vulnerability is high, especially if your website uses content indexing services (like Find or other search engines). Mitigation  The issue has been fixed in EPiServer.Forms <a href="https://nuget.optimizely.com/package/?id=EPiServer.Forms&v=5.7.0">v5.7.0</a> (<a href="/link/1933ba72787346df9003b7a4c7d1cff8.aspx?epsremainingpath=bug/AFORM-3620">AFORM-3620</a>) for CMS 12 and <a href="https://nuget.optimizely.com/package/?id=EPiServer.Forms&v=4.31.0">v4.31.</a><a href="https://nuget.optimizely.com/package/?id=EPiServer.Forms&v=4.31.0">0</a> for CMS 11. Please upgrade to those versions as soon as possible. For DXP service customers: <ul> <li>Mitigation is in place for all DXP service customers.</li> <li>Update (October 27): To clarify, we have mitigated existing vulnerable vectors, but packages SHOULD be updated to mitigate the risk of reintroducing the vulnerability!</li> </ul> Affected versions Any Forms version before 5.7.0 (CMS12) or Forms 4.31.0 (CMS11).  Remediation If using the affected versions of EPiServer.Forms listed above, please update to version 5.7.0 (CMS12) or Forms 4.31.0 (CMS11). Please reach out to our support for further guidance by email to <a href="mailto:support@optimizely.com">support@optimizely.com</a> or submit a request at <a href="https://support.optimizely.com/hc/en-us">https://support.optimizely.com/hc/en-us</a>. <h3>Questions</h3> If you have any questions, please contact our support team (with assistance from our security engineering team) at <a href="mailto:support@optimizely.com">support@optimizely.com</a>. <h3>Risk definitions</h3> Low – little to no potential impact on Optimizely or customer environments/data. Vulnerability has low exploitability, for example: requirement for local or physical system access, zero reachability to/executability within Optimizely products/code. Medium – some potential impact on Optimizely or customer environments/data. Vulnerability has medium exploitability, for example: requirement to be located on the same local network as the target, requirement for an individual to be manipulated via social engineering, requirement for user privileges, vulnerability achieves limited access to Optimizely products/code. High – high potential impact on Optimizely or customer environments/data.  Vulnerability has high exploitability, for example:  achieves high level access to Optimizely products/code, could elevate privileges, could result in a significant data loss or downtime. Critical – very significant potential impact on Optimizely or customer environments/data.  Vulnerability has very high exploitability, for example: achieves admin/root-level access to Optimizely products/code.  Vulnerability does not require any special authentication credentials/knowledge of Optimizely products/environments.2023-10-25T04:10:08.0000000Z

Blog post

Forms 4.6 performance enhancement<!DOCTYPE html> <html> <head> </head> <body> After using DotTrace and Jmeter to analyze Forms performance issues, we found some problematic code segments, which created issues like slow response time or high CPU usage. Therefore, we internally changed the Forms API in order to reduce data processing time. From version 4.6.0, Forms with DDS as the default data storage mechanism has much better performance compared to the previous versions, especially for forms with a large number of submissions. Below is a performance comparison of Forms 4.6.0 and 4.5.1. Our comparison uses Jmeter with more than 20,000 records (all tests are run on the developer's computer). Forms 4.6.0 takes about 30 seconds to finish the test. <img src="/link/15b11db79eac416aa83db2da7c543f21.aspx" width="1079" alt="4.6" height="426" /> Forms 4.5.1 takes more than 3 hours to finish that test. <img src="/link/138cf9ba3628474d86e3decc107caf08.aspx" width="1093" alt="4.5.1" height="505" /> We ran another test, and the results looks quite promising when comparing MongoDB to DDS as the data storage mechanism. <img src="/link/f611e4fbe86844708e901c2587c08c40.aspx" width="1343" alt="DDS and MongoDB" height="344" /> </body> </html>2017-08-03T06:12:02.0000000Z

Blog post