Yes, there is a version jump compared to the previous 7.44 release; this is to indicate that this Drupal 7 point release is a bit larger than past ones and makes a few more changes and new features available than normal.
Updating your existing Drupal 7 sites is recommended. Backwards compatibility is still being maintained, although read on to find out about a couple of changes that might need your attention during the update.
Yes, there is a version jump compared to the previous 7.44 release; this is to indicate that this Drupal 7 point release is a bit larger than past ones and makes a few more changes and new features available than normal.
Updating your existing Drupal 7 sites is recommended. Backwards compatibility is still being maintained, although read on to find out about a couple of changes that might need your attention during the update.
Script based on guidelines given above
If you need to fix permissions repeatedly then the following script will help you, it is based on the guidelines given above and performs some checks before any modification to ensure it is not applied on files/directories outside your Drupal installation.
Script based on guidelines given above
If you need to fix permissions repeatedly then the following script will help you, it is based on the guidelines given above and performs some checks before any modification to ensure it is not applied on files/directories outside your Drupal installation.
Security Review runs the following checks:
Safe file system permissions (protecting against arbitrary code execution)
Text formats don't allow dangerous tags (protecting against XSS)
PHP or Javascript in content (nodes and comments and fields in Drupal 7)
Safe error reporting (avoiding information disclosure)
Secure private files
Only safe upload extensions
Large amount of database errors (could be sign of SQLi attempts)
Large amount of failed logins (could be sign of brute-force attempts)
Responsible Drupal admin permissions (protecting against access misconfiguration)
Username as password (
Security Review runs the following checks:
Safe file system permissions (protecting against arbitrary code execution)
Text formats don't allow dangerous tags (protecting against XSS)
PHP or Javascript in content (nodes and comments and fields in Drupal 7)
Safe error reporting (avoiding information disclosure)
Secure private files
Only safe upload extensions
Large amount of database errors (could be sign of SQLi attempts)
Large amount of failed logins (could be sign of brute-force attempts)
Responsible Drupal admin permissions (protecting against access misconfiguration)
Username as password (
Security Review runs the following checks:
Safe file system permissions (protecting against arbitrary code execution)
Text formats don't allow dangerous tags (protecting against XSS)
PHP or Javascript in content (nodes and comments and fields in Drupal 7)
Safe error reporting (avoiding information disclosure)
Secure private files
Only safe upload extensions
Large amount of database errors (could be sign of SQLi attempts)
Large amount of failed logins (could be sign of brute-force attempts)
Responsible Drupal admin permissions (protecting against access misconfiguration)
Username as password (
Recently, a security researcher reported some vulnerabilities to the Drupal Security Team. The Security Team and researcher worked together to understand the risks and decided that the potential impact was small enough that the reported problems could be fixed in public and that the researcher would write a blog post with their perspective on the situation. Below are some quotes of the critical issues from the blog post and the Drupal Security Team’s analysis of the risks.
Recently, a security researcher reported some vulnerabilities to the Drupal Security Team. The Security Team and researcher worked together to understand the risks and decided that the potential impact was small enough that the reported problems could be fixed in public and that the researcher would write a blog post with their perspective on the situation. Below are some quotes of the critical issues from the blog post and the Drupal Security Team’s analysis of the risks.
Recently, a security researcher reported some vulnerabilities to the Drupal Security Team. The Security Team and researcher worked together to understand the risks and decided that the potential impact was small enough that the reported problems could be fixed in public and that the researcher would write a blog post with their perspective on the situation. Below are some quotes of the critical issues from the blog post and the Drupal Security Team’s analysis of the risks.