Acronym fix for CORS

bugcrowd · Nov 29, 2023 · 14211c7 · 14211c7
1 parent 77ef813
commit 14211c7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/...curity_misconfiguration/unsafe_cross_origin_resource_sharing/recommendations.md b/...curity_misconfiguration/unsafe_cross_origin_resource_sharing/recommendations.md
@@ -1,6 +1,6 @@
 # Recommendation(s)
 
-To prevent CORS attacks the cross-origin requests need to be properly configured. This includes not using `null` and instead using a strict allow list of trusted sites in the `Access-Control-Allow-Origin` header. It is also good practice to not use wildcards (`*`) for internal networks, and include further server-side protections for sensitive data.
+To prevent Cross-Origin Resource Sharing (CORS) attacks the cross-origin requests need to be properly configured. This includes not using `null` and instead using a strict allow list of trusted sites in the `Access-Control-Allow-Origin` header. It is also good practice to not use wildcards (`*`) for internal networks, and include further server-side protections for sensitive data.
 
 For more information, please see:
 

diff --git a/...rver_security_misconfiguration/unsafe_cross_origin_resource_sharing/template.md b/...rver_security_misconfiguration/unsafe_cross_origin_resource_sharing/template.md
@@ -1,4 +1,4 @@
-# Unsafe Cross-Origin Resource Sharing
+# Unsafe Cross-Origin Resource Sharing (CORS)
 
 ## Overview of the Vulnerability