Is elkcountyfoundation.org secure and safe to use? | Web Security Optimization (WSO) report by Idyllum Labs.

bot@idyllum:~$ Please wait, the scan will start shortly

bot@idyllum:~$ Scanning: /100

bot@idyllum:~$ Latest scan is in long queue and may take a while

bot@idyllum:~$ Web Security Optimization (WSO) scan failed! Please try again

This site redirects to

Invalid domain!

Please log in or sign up for a free account to see this report in its entirety!

# Website security scan results for elkcountyfoundation.org

------------------

## At a glance

Site scanned: elkcountyfoundation.org
Risk level: MEDIUM
WSO score: 85 / 100
Ranks: worse than 72.9% of tested sites
Date of scan: Jan. 15, 2022, 8 a.m.
SSL Status: [OK] SSL Encryption enforced
Total alerts: 85

## Verdict

Average! This website can be considered safe. But there is room for easy improvement! Please forward this report to the web development team and we are sure they can find some ways to secure the site even more.

# Environment info

------------------

## Server

IP: 74.81.107.44
Location: United States
Web server: Apache

## CMS

WordPress (5.8.1)

## Technology

Apache
JQuery (3.6.0)

## Uncategorized

RedirectLocation (https://elkcountyfoundation.org/)
Cookies (PHPSESSID)
UncommonHeaders (x-redirect-by)
Title (Elk County Community Foundation – Building A Path To Tomorrow)
Email (['eccf@elkcountyfoundation.org'])
HTML5
MetaGenerator (['WordPress 5.8.1'])
Script (['text/javascript'])

# 10 Open ports for elkcountyfoundation.org (Nmap scan)

------------------
Port 21 (tcp) - ftp
Port 25 (tcp) - smtp
Port 53 (tcp) - domain
Port 80 (tcp) - http
Port 110 (tcp) - pop3
Port 143 (tcp) - imap
Port 443 (tcp) - https
Port 587 (tcp) - submission
Port 993 (tcp) - imaps
Port 995 (tcp) - pop3s

# OWASP ZAP scan results

------------------

## Informative alerts

[OK] PASSED Charset Mismatch
[+]
[OK] PASSED Content-Type Header Empty
[+]
[OK] PASSED Content-Type Header Missing
[+]
[OK] PASSED CSP: Notices
[+]
[OK] PASSED CSP Scanner: Notices
[+]
[OK] PASSED CSP Scanner: X-Content-Security-Policy
[+]
[OK] PASSED CSP Scanner: X-WebKit-CSP
[+]
[OK] PASSED CSP: X-Content-Security-Policy
[+]
[OK] PASSED CSP: X-WebKit-CSP
[+]
[OK] PASSED Information Disclosure - Sensitive Information in HTTP Referrer Header
[+]
[OK] PASSED Information Disclosure - Sensitive Information in URL
[+]
[!!] FAILED Information Disclosure - Suspicious Comments
[+]
What does this mean?

The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.

Where exactly is this vulnerability found?
How to solve this?

Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.

[OK] PASSED Loosely Scoped Cookie
[+]
[OK] PASSED Split Viewstate in Use
[+]
[!!] FAILED Timestamp Disclosure - Unix
[+]
What does this mean?

A timestamp was disclosed by the application/web server - Unix

Where exactly is this vulnerability found?
How to solve this?

Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.

[OK] PASSED Username Hash Found
[+]
[OK] PASSED WSDL File Detection
[+]
[OK] PASSED WSDL File Passive Scanner
[+]

## Low risk vulnerabilities

[!!] FAILED Absence of Anti-CSRF Tokens
[+]
What does this mean?

No Anti-CSRF tokens were found in a HTML submission form.A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.CSRF attacks are effective in a number of situations, including: * The victim has an active session on the target site. * The victim is authenticated via HTTP auth on the target site. * The victim is on the same local network as the target site.CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.

Where exactly is this vulnerability found?
How to solve this?

Phase: Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.For example, use anti-CSRF packages such as the OWASP CSRFGuard.Phase: ImplementationEnsure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.Phase: Architecture and DesignGenerate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).Note that this can be bypassed using XSS.Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.Note that this can be bypassed using XSS.Use the ESAPI Session Management control.This control includes a component for CSRF.Do not use the GET method for any request that triggers a state change.Phase: ImplementationCheck the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.

[OK] PASSED Application Error Disclosure
[+]
[!!] FAILED Cookie No HttpOnly Flag
[+]
What does this mean?

A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.

Where exactly is this vulnerability found?
How to solve this?

Ensure that the HttpOnly flag is set for all cookies.

[!!] FAILED Cookie Without SameSite Attribute
[+]
What does this mean?

A cookie has been set without the SameSite attribute, which means that the cookie can be sent as a result of a 'cross-site' request. The SameSite attribute is an effective counter measure to cross-site request forgery, cross-site script inclusion, and timing attacks.

Where exactly is this vulnerability found?
How to solve this?

Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.

[!!] FAILED Cookie Without Secure Flag
[+]
What does this mean?

A cookie has been set without the secure flag, which means that the cookie can be accessed via unencrypted connections.

Where exactly is this vulnerability found?
How to solve this?

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

[OK] PASSED Cross-Domain JavaScript Source File Inclusion
[+]
[!!] FAILED Incomplete or No Cache-control and Pragma HTTP Header Set
[+]
What does this mean?

The cache-control and pragma HTTP header have not been set properly or are missing allowing the browser and proxies to cache content.

Where exactly is this vulnerability found?
How to solve this?

Whenever possible ensure the cache-control HTTP header is set with no-cache, no-store, must-revalidate; and that the pragma HTTP header is set with no-cache.

[OK] PASSED Information Disclosure - Debug Error Messages
[+]
[OK] PASSED Old Asp.Net Version in Use
[+]
[OK] PASSED Private IP Disclosure
[+]
[OK] PASSED Referer Exposes Session ID
[+]
[OK] PASSED Secure Pages Include Mixed Content
[+]
[OK] PASSED Server Leaks Information via "X-Powered-By" HTTP Response Header Field(s)
[+]
[OK] PASSED Web Browser XSS Protection Not Enabled
[+]
[OK] PASSED X-AspNet-Version Response Header
[+]
[!!] FAILED X-Content-Type-Options Header Missing
[+]
What does this mean?

The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.

Where exactly is this vulnerability found?
How to solve this?

Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.

[OK] PASSED X-Debug-Token Information Leak
[+]

## Medium risk vulnerabilities

[OK] PASSED Cross-Domain Misconfiguration
[+]
[OK] PASSED CSP Scanner: script-src unsafe-inline
[+]
[OK] PASSED CSP Scanner: style-src unsafe-inline
[+]
[OK] PASSED CSP Scanner: Wildcard Directive
[+]
[OK] PASSED CSP: script-src unsafe-inline
[+]
[OK] PASSED CSP: style-src unsafe-inline
[+]
[OK] PASSED CSP: Wildcard Directive
[+]
[OK] PASSED Emails Found in the Viewstate
[+]
[OK] PASSED HTTP Parameter Override
[+]
[OK] PASSED Insecure JSF ViewState
[+]
[OK] PASSED Multiple X-Frame-Options Header Entries
[+]
[OK] PASSED Potential IP Addresses Found in the Viewstate
[+]
[OK] PASSED Session ID in URL Rewrite
[+]
[OK] PASSED Vulnerable JS Library
[+]
[OK] PASSED Weak Authentication Method
[+]
[OK] PASSED X-Frame-Options Defined via META (Non-compliant with Spec)
[+]
[!!] FAILED X-Frame-Options Header Not Set
[+]
What does this mean?

X-Frame-Options header is not included in the HTTP response to protect against 'ClickJacking' attacks.

Where exactly is this vulnerability found?
How to solve this?

Most modern Web browsers support the X-Frame-Options HTTP header. Ensure it's set on all web pages returned by your site (if you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. ALLOW-FROM allows specific websites to frame the web page in supported web browsers).

[OK] PASSED X-Frame-Options Setting Malformed
[+]

## High risk vulnerabilities

[OK] PASSED Viewstate without MAC Signature (Sure)
[+]
[OK] PASSED Viewstate without MAC Signature (Unsure)
[+]

Manual inspection results

This site has not been manually inspected yet. Please apply for an inspection here

Find this WSO report online:

# Idyllum Labs is on a mission

------------------

Is the code hosted at elkcountyfoundation.org vulnerable to cybersecurity attacks? Are the used systems up to date and respecting the security standards of 2022?

We at Idyllum Labs wanted to find out! That is why we built this automated website security scanner and generated this report.

# Please note

This is an automated and unbiased website vulnerability scan for the domain elkcountyfoundation.org and has nothing to do with human subjectivity, thoughts, opinions, or relationships.

Our cloud-based infrastructure crawls the internet using a mixture of OWASP ZAP, Nmap, Whatweb, and other great software to detect website security issues. We display this data for educational purposes - to give security guidelines for anyone interested in building a safer web environment.

It is important to understand that we don't gather business information. We analyze used technology and are not interested in

If you have comments, don't agree with the results, or want to submit a site for manual examination, don't hesitate to contact us.


Run a free OWASP ZAP scan for any website at Idyllum.com!

# What next?

------------------

## Dig deeper

  1. Log in or create a free account to gain access to this report in its entirety.
  2. Use our dashboard to automate security testing and set up automatic monitoring for your website portfolio.
  3. Scan a new domain or initiate a rescan for this domain.

# Join our ranks

  1. Use these insights to build your systems bullet-proof.
  2. Explore our datasets and compare your results.
  3. Drop us a line! Help us expand our code or cloud or just say hi!
  4. Support the cause - your donation helps to keep this service free and unbiased.

Want to scan and monitor multiple sites at once?

Create an account
Yes, generating security reports with Idyllum Labs is free!
(Just as all the best things in life..)