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 273
  • Vulnerability42
  • Bug51
  • Security Hotspot34
  • Code Smell146
Filtered: 70 rules found
cwe
    Impact
      Clean code attribute
        1. The number of arguments passed to a function should match the number of parameters

           Bug
        2. Non-empty statements should change control flow or have at least one side-effect

           Bug
        3. Variables should be initialized before use

           Bug
        4. Server-side requests should not be vulnerable to traversing attacks

           Vulnerability
        5. Credentials should not be hard-coded

           Vulnerability
        6. Hard-coded secrets are security-sensitive

           Security Hotspot
        7. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        8. Allowing unfiltered HTML content in WordPress is security-sensitive

           Security Hotspot
        9. Allowing all external requests from a WordPress server is security-sensitive

           Security Hotspot
        10. WordPress theme and plugin editors are security-sensitive

           Security Hotspot
        11. Applications should not create session cookies from untrusted input

           Vulnerability
        12. Reflection should not be vulnerable to injection attacks

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

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

           Vulnerability
        15. Authorizations should be based on strong decisions

           Vulnerability
        16. Allowing requests with excessive content length is security-sensitive

           Security Hotspot
        17. Cipher algorithms should be robust

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

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

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

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

           Vulnerability
        22. Using clear-text protocols is security-sensitive

           Security Hotspot
        23. Manual generation of session ID is security-sensitive

           Security Hotspot
        24. HTTP request redirections should not be open to forging attacks

           Vulnerability
        25. Logging should not be vulnerable to injection attacks

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

           Vulnerability
        27. Deserialization should not be vulnerable to injection attacks

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

           Vulnerability
        29. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

           Security Hotspot
        30. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        31. Server certificates should be verified during SSL/TLS connections

           Vulnerability
        32. Signaling processes is security-sensitive

           Security Hotspot
        33. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        34. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        35. Disabling CSRF protections is security-sensitive

           Security Hotspot
        36. LDAP connections should be authenticated

           Vulnerability
        37. Cryptographic keys should be robust

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

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

           Vulnerability
        40. "cgi.force_redirect" should be enabled

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

           Vulnerability
        42. "open_basedir" should limit file access

           Vulnerability
        43. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        44. XML parsers should not be vulnerable to XXE attacks

           Vulnerability
        45. Multiline blocks should be enclosed in curly braces

           Code Smell
        46. Regular expressions should not be vulnerable to Denial of Service attacks

           Vulnerability
        47. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        48. Neither DES (Data Encryption Standard) nor DESede (3DES) should be used

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

           Vulnerability
        50. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        51. A secure password should be used when connecting to a database

           Vulnerability
        52. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        53. XPath expressions should not be vulnerable to injection attacks

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

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

           Vulnerability
        56. Formatting SQL queries is security-sensitive

           Security Hotspot
        57. OS commands should not be vulnerable to command injection attacks

           Vulnerability
        58. Hard-coded credentials are security-sensitive

           Security Hotspot
        59. Password hashing functions should use an unpredictable salt

           Vulnerability
        60. References should not be passed to function calls

           Code Smell
        61. Unused assignments should be removed

           Code Smell
        62. All code should be reachable

           Bug
        63. Dynamically executing code is security-sensitive

           Security Hotspot
        64. "switch" statements should have "default" clauses

           Code Smell
        65. Switch cases should end with an unconditional "break" statement

           Code Smell
        66. Useless "if(true) {...}" and "if(false){...}" blocks should be removed

           Bug
        67. Track uses of "TODO" tags

           Code Smell
        68. Track uses of "FIXME" tags

           Code Smell
        69. Assignments should not be made from within sub-expressions

           Code Smell
        70. Generic exceptions ErrorException, RuntimeException and Exception should not be thrown

           Code Smell

        Creating cookies without the "secure" flag is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe
        • privacy

        When a cookie is protected with the secure attribute set to true it will not be send by the browser over an unencrypted HTTP request and thus cannot be observed by an unauthorized person during a man-in-the-middle attack.

        Ask Yourself Whether

        • the cookie is for instance a session-cookie not designed to be sent over non-HTTPS communication.
        • it’s not sure that the website contains mixed content or not (ie HTTPS everywhere or not)

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • It is recommended to use HTTPs everywhere so setting the secure flag to true should be the default behaviour when creating cookies.
        • Set the secure flag to true for session-cookies.

        Sensitive Code Example

        In php.ini you can specify the flags for the session cookie which is security-sensitive:

        session.cookie_secure = 0; // Sensitive: this security-sensitive session cookie is created with the secure flag set to false (cookie_secure = 0)
        

        Same thing in PHP code:

        session_set_cookie_params($lifetime, $path, $domain, false);
        // Sensitive: this security-sensitive session cookie is created with the secure flag (the fourth argument) set to _false_
        

        If you create a custom security-sensitive cookie in your PHP code:

        $value = "sensitive data";
        setcookie($name, $value, $expire, $path, $domain, false);  // Sensitive: a security-sensitive cookie is created with the secure flag  (the sixth argument) set to _false_
        

        By default setcookie and setrawcookie functions set the sixth argument / secure flag to false:

        $value = "sensitive data";
        setcookie($name, $value, $expire, $path, $domain);  // Sensitive: a security-sensitive cookie is created with the secure flag (the sixth argument) not defined (by default to false)
        setrawcookie($name, $value, $expire, $path, $domain);  // Sensitive: a security-sensitive cookie is created with the secure flag (the sixth argument) not defined (by default to false)
        

        Compliant Solution

        session.cookie_secure = 1; // Compliant: the sensitive cookie will not be send during an unencrypted HTTP request thanks to cookie_secure property set to 1
        
        session_set_cookie_params($lifetime, $path, $domain, true); // Compliant: the sensitive cookie will not be send during an unencrypted HTTP request thanks to the secure flag (the fouth argument) set to true
        
        $value = "sensitive data";
        setcookie($name, $value, $expire, $path, $domain, true); // Compliant: the sensitive cookie will not be send during an unencrypted HTTP request thanks to the secure flag (the sixth  argument) set to true
        setrawcookie($name, $value, $expire, $path, $domain, true);// Compliant: the sensitive cookie will not be send during an unencrypted HTTP request thanks to the secure flag (the sixth argument) set to true
        

        See

        • OWASP - Top 10 2021 Category A4 - Insecure Design
        • OWASP - Top 10 2021 Category A5 - Security Misconfiguration
        • OWASP - Top 10 2017 Category A3 - Sensitive Data Exposure
        • CWE - CWE-311 - Missing Encryption of Sensitive Data
        • CWE - CWE-315 - Cleartext Storage of Sensitive Information in a Cookie
        • CWE - CWE-614 - Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
        • STIG Viewer - Application Security and Development: V-222576 - The application must set the secure flag on session cookies.
          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

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use