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: 18 rules found
injection
    Impact
      Clean code attribute
        1. Server-side requests should not be vulnerable to traversing attacks

           Vulnerability
        2. Constructing arguments of system commands from user input is security-sensitive

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

           Vulnerability
        4. Reflection should not be vulnerable to injection attacks

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

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

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

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

           Vulnerability
        9. Logging should not be vulnerable to injection attacks

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

           Vulnerability
        11. Deserialization should not be vulnerable to injection attacks

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

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

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

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

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

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

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

           Vulnerability

        Applications should not create session cookies from untrusted input

        intentionality - complete
        security
        Vulnerability
        • cwe
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        Session Cookie Injection occurs when a web application assigns session cookies to users using untrusted data.

        Session cookies are used by web applications to identify users. Thus, controlling these enable control over the identity of the users within the application.

        The injection might occur via a GET parameter, and the payload, for example, https://example.com?cookie=injectedcookie, delivered using phishing techniques.

        What is the potential impact?

        A well-intentioned user opens a malicious link that injects a session cookie in their web browser. This forces the user into unknowingly browsing a session that isn’t theirs.

        Below are some real-world scenarios that illustrate some impacts of an attacker exploiting the vulnerability.

        Sensitive data disclosure

        A victim introduces sensitive data within the attacker’s application session that can later be retrieved by them. This can lead to a variety of implications depending on what type of data is disclosed. Strictly confidential user data or organizational data leakage have different impacts.

        Vulnerability chaining

        An attacker not only manipulates a user into browsing an application using a session cookie of their control but also successfully detects and exploits a self-XSS on the target application.
        The victim browses the vulnerable page using the attacker’s session and is affected by the XSS, which can then be used for a wide range of attacks including credential stealing using mirrored login pages.

          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.2

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use