Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

How to Disable Groovy Scripts and the Scripting Console in Control Panel - DXP 7.4

Written By

Solyom Nagy-Györkös

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • I want to disable Groovy Scripts from being executed in Control Panel's Server Administration panel

Environment

  • DXP 7.4

Resolution

  • Approach 1:
  • Approach 2:
    1. Go to Control Panel > Configuration > System Settings

    2. In the Platform section, find "Module Container"

    3. Navigate to Global Menu > System Settings > Module Container > Component Blacklist tab
    4. Add com.liferay.server.admin.web.internal.scripting.ServerScripting to 
      Blacklist Component Names
    5. Save

Additional Information

  • Security Statement on CVE-2019-11444: Disputed Groovy Script console vulnerability
  • How to Disable Groovy Scripts and the Scripting Console in Control Panel
  • This will disable all actions about Server Administration because “com.liferay.server.admin.web.internal.portlet.action.EditServerMVCActionCommand” reference ServerScripting.
  • Disabling Groovy scripting entirely by blacklisting com.liferay.server.admin.web.internal.scripting.ServerScripting not only causes several console errors when attempting to run Groovy scripts (although it does prevent them from running) but it is also not effective, because a user that has permission to blacklist modules in this way can just remove the blacklisted module again and continue to run scripts.
  • As of 2023.Q4.0, blacklisting the aforementioned component components doesn't work either because the functionality was refactored to a Java util class com.liferay.server.admin.web.internal.scripting.util.ServerScriptingUtil.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?