Vulnerabilities and Securities

All software can have security vulnerabilities. ScriptRunner uses a number of open-source libraries, similar to most apps on the Marketplace. This page covers how we scan for vulnerabilities and common security concerns. 

Privacy and security information on Atlassian Marketplace

You can also view security details when you select the Privacy and Security tab on the ScriptRunner Atlassian Marketplace listing. 

Vulnerability scanning

During every build, we scan all dependencies for known vulnerabilities as cataloged by the National Vulnerability Database. Where we find a vulnerability we endeavor to upgrade that dependency to a version without the vulnerability. 

Check out our blog on vulnerabilities for more detail and an example of how we've dealt with vulnerabilities in the past. 


We do not always take action when a vulnerability is identified. This is because:

  • Some vulnerabilities are not exploitable through ScriptRunner, or to exploit them would require system administrator access. 
  • Some vulnerabilities are disputed by the library authors.
  • Sometimes the scanner produces false positives.

Read Atlassian's Security page for more details on security, advisories, and best practices. 

Security concerns

Sometimes we get reports that ScriptRunner is insecure because, for instance, you can execute a command line program on the Confluence Cloud using the Script Console.

The philosophy of ScriptRunner is to make programming tasks easy. You could write an app in Java, install it in Confluence Cloud, and it could execute a command line program, or you could do it in ScriptRunner. Therefore, everything you can do in an app you can do in ScriptRunner. 

Restricting scripting permissions

To upload an app, you need Confluence Cloud System administrator permission. By default, to author and/or run a ScriptRunner script, you must have Confluence Cloud administrator permissions.

For more details, check out the Permissions page.

On this page