SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
PHP

PHP static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your PHP code

  • All rules 263
  • Vulnerability54
  • Bug51
  • Security Hotspot12
  • Code Smell146
 
Tags
    Impact
      Clean code attribute
        1. Server-side requests should not be vulnerable to traversing attacks

           Vulnerability
        2. Credentials should not be hard-coded

           Vulnerability
        3. Secrets should not be hard-coded

           Vulnerability
        4. Prevent unfiltered HTML exposure in WordPress for enhanced security

           Vulnerability
        5. Prevent unauthenticated WordPress database repair for enhanced security

           Vulnerability
        6. External requests should be restricted in WordPress to prevent data leaks and SSRF

           Vulnerability
        7. Automatic updates should not be disabled

           Vulnerability
        8. Disable direct file editing in WordPress admin interface

           Vulnerability
        9. Secret keys and salt values should be robust

           Vulnerability
        10. Applications should not create session cookies from untrusted input

           Vulnerability
        11. Reflection should not be vulnerable to injection attacks

           Vulnerability
        12. OS commands should not be vulnerable to argument injection attacks

           Vulnerability
        13. A new session should be created during user authentication

           Vulnerability
        14. Authorizations should be based on strong decisions

           Vulnerability
        15. Cipher algorithms should be robust

           Vulnerability
        16. Encryption algorithms should be used with secure mode and padding scheme

           Vulnerability
        17. Server hostnames should be verified during SSL/TLS connections

           Vulnerability
        18. Include expressions should not be vulnerable to injection attacks

           Vulnerability
        19. Dynamic code execution should not be vulnerable to injection attacks

           Vulnerability
        20. Session IDs must be securely generated and not user-specified

           Vulnerability
        21. HTTP request redirections should not be open to forging attacks

           Vulnerability
        22. Logging should not be vulnerable to injection attacks

           Vulnerability
        23. Server-side requests should not be vulnerable to forging attacks

           Vulnerability
        24. Deserialization should not be vulnerable to injection attacks

           Vulnerability
        25. Endpoints should not be vulnerable to reflected cross-site scripting (XSS) attacks

           Vulnerability
        26. Avoid overly permissive Cross-Origin Resource Sharing (CORS) policies to enhance security

           Vulnerability
        27. Server certificates should be verified during SSL/TLS connections

           Vulnerability
        28. Deactivate debugging features before deploying to production

           Vulnerability
        29. LDAP connections should be authenticated

           Vulnerability
        30. Cryptographic keys should be robust

           Vulnerability
        31. Weak SSL/TLS protocols should not be used

           Vulnerability
        32. Database queries should not be vulnerable to injection attacks

           Vulnerability
        33. "file_uploads" should be disabled

           Vulnerability
        34. "enable_dl" should be disabled

           Vulnerability
        35. "session.use_trans_sid" should not be enabled

           Vulnerability
        36. "cgi.force_redirect" should be enabled

           Vulnerability
        37. "allow_url_fopen" and "allow_url_include" should be disabled

           Vulnerability
        38. "open_basedir" should limit file access

           Vulnerability
        39. Session-management cookies should not be persistent

           Vulnerability
        40. "sleep" should not be called

           Vulnerability
        41. XML parsers should not be vulnerable to XXE attacks

           Vulnerability
        42. Regular expressions should not be vulnerable to Denial of Service attacks

           Vulnerability
        43. Avoid overly permissive POSIX file permissions to enhance security

           Vulnerability
        44. Neither DES (Data Encryption Standard) nor DESede (3DES) should be used

           Vulnerability
        45. Cryptographic RSA algorithms should always incorporate OAEP (Optimal Asymmetric Encryption Padding)

           Vulnerability
        46. A secure password should be used when connecting to a database

           Vulnerability
        47. XPath expressions should not be vulnerable to injection attacks

           Vulnerability
        48. I/O function calls should not be vulnerable to path injection attacks

           Vulnerability
        49. LDAP queries should not be vulnerable to injection attacks

           Vulnerability
        50. Use prepared statements to securely construct SQL queries

           Vulnerability
        51. OS commands should not be vulnerable to command injection attacks

           Vulnerability
        52. SHA-1 and Message-Digest hash algorithms should not be used in secure contexts

           Vulnerability
        53. Credentials should not be hard-coded

           Vulnerability
        54. Password hashing functions should use an unpredictable salt

           Vulnerability

        Secret keys and salt values should be robust

        responsibility - trustworthy
        security
        Vulnerability

          Why is this an issue?

          More Info

          Secret keys are used in combination with an algorithm to encrypt data. A typical use case is an authentication system. For such a system to be secure, the secret key should have a value which cannot be guessed and which is long enough to not be vulnerable to brute-force attacks.

          A "salt" is an extra piece of data which is included when hashing data such as a password. Its value should have the same properties as a secret key.

          This rule raises an issue when it detects that a secret key or a salt has a predictable value or that it’s not long enough.

          Noncompliant code example

          WordPress:

          define('AUTH_KEY', 'hello'); // Noncompliant
          define('AUTH_SALT', 'hello'); // Noncompliant
          define('AUTH_KEY', 'put your unique phrase here'); // Noncompliant, this is the default value
          

          Compliant solution

          WordPress:

          define('AUTH_KEY', 'D&ovlU#|CvJ##uNq}bel+^MFtT&.b9{UvR]g%ixsXhGlRJ7q!h}XWdEC[BOKXssj');
          define('AUTH_SALT', 'FIsAsXJKL5ZlQo)iD-pt??eUbdc{_Cn<4!d~yqz))&B D?AwK%)+)F2aNwI|siOe');
          
            Available In:
          • SonarQube IdeCatch issues on the fly,
            in your IDE
          • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
          • SonarQube Community BuildAnalyze code in your
            on-premise CI
            Available Since
            9.1
          • SonarQube ServerAnalyze code in your
            on-premise CI
            Developer Edition
            Available Since
            9.1

          © 2025 SonarSource Sàrl. All rights reserved.

          Privacy Policy | Cookie Policy | Terms of Use