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

        Server certificates should be verified during SSL/TLS connections

        responsibility - trustworthy
        security
        Vulnerability
        • cwe
        • privacy
        • ssl

        This vulnerability makes it possible that an encrypted communication is intercepted.

        Why is this an issue?

        How can I fix it?

        More Info

        Transport Layer Security (TLS) provides secure communication between systems over the internet by encrypting the data sent between them. Certificate validation adds an extra layer of trust and security to this process to ensure that a system is indeed the one it claims to be.

        When certificate validation is disabled, the client skips a critical security check. This creates an opportunity for attackers to pose as a trusted entity and intercept, manipulate, or steal the data being transmitted.

        What is the potential impact?

        Establishing trust in a secure way is a non-trivial task. When you disable certificate validation, you are removing a key mechanism designed to build this trust in internet communication, opening your system up to a number of potential threats.

        Identity spoofing

        If a system does not validate certificates, it cannot confirm the identity of the other party involved in the communication. An attacker can exploit this by creating a fake server and masquerading as a legitimate one. For example, they might set up a server that looks like your bank’s server, tricking your system into thinking it is communicating with the bank. This scenario, called identity spoofing, allows the attacker to collect any data your system sends to them, potentially leading to significant data breaches.

        Loss of data integrity

        When TLS certificate validation is disabled, the integrity of the data you send and receive cannot be guaranteed. An attacker could modify the data in transit, and you would have no way of knowing. This could range from subtle manipulations of the data you receive to the injection of malicious code or malware into your system. The consequences of such breaches of data integrity can be severe, depending on the nature of the data and the system.

          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