Vulnerability Scan Result

Target:

https://bcfoodsafety.ca/

Scanned target: https://bcfoodsafety.ca/

Submitted: Dec 04, 2025 from SL

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	BC Food Safety - For the Love of Skills
Description:	Ensuring Foods Processed in BC Are the Safest Across the Country and the World.

IP Information

ip_address	159.203.191.200
country	US
network_name	Digitalocean LLC
asn	AS14061

Open Ports

80/tcp	http	Apache httpd 2.4.41
443/tcp	https	Apache httpd 2.4.41

Web Technologies

Software / Version	Category
Animate.css	UI frameworks
Contact Form 7	WordPress plugins, Form builders
Font Awesome	Font scripts
Adobe Fonts	Font scripts
jQuery Migrate 3.4.1	JavaScript libraries
core-js 3.35.1	JavaScript libraries
Google Font API	Font scripts
GSAP	JavaScript frameworks
Apache HTTP Server 2.4.41	Web servers
Isotope	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Modernizr 2.6.2	JavaScript libraries
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
Skrollr 0.6.29	JavaScript libraries
Typekit	Font scripts
Underscore.js	JavaScript libraries
Priority Hints	Performance
WooCommerce	Ecommerce, WordPress plugins
WordPress	CMS, Blogs
WordPress Multisite	Hosting
wpBakery	Page builders, WordPress plugins
jsDelivr	CDN
Max Mega Menu	Widgets, WordPress plugins
RSS	Miscellaneous
Slider Revolution 6.6.19	Widgets, Photo galleries
Ubuntu	Operating systems
W3 Total Cache	Caching, WordPress plugins
Cart Functionality	Ecommerce
Yoast SEO 22.8	SEO, WordPress plugins

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2024-38476	9.8	0.01813	0.82344	Vulnerability in core of Apache HTTP Server 2.4.59 and earlier are vulnerably to information disclosure, SSRF or local script execution via backend applications whose response headers are malicious or exploitable. Users are recommended to upgrade to version 2.4.60, which fixes this issue.
CVE-2024-38474	9.8	0.00436	0.62288	Substitution encoding issue in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows attacker to execute scripts in directories permitted by the configuration but not directly reachable by any URL or source disclosure of scripts meant to only to be executed as CGI. Users are recommended to upgrade to version 2.4.60, which fixes this issue. Some RewriteRules that capture and substitute unsafely will now fail unless rewrite flag "UnsafeAllow3F" is specified.
CVE-2023-25690	9.8	0.56875	0.98028	Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied request-target (URL) data and is then re-inserted into the proxied request-target using variable substitution. For example, something like: RewriteEngine on RewriteRule "^/here/(.*)" "http://example.com:8080/elsewhere?$1"; [P] ProxyPassReverse /here/ http://example.com:8080/ Request splitting/smuggling could result in bypass of access controls in the proxy server, proxying unintended URLs to existing origin servers, and cache poisoning. Users are recommended to update to at least version 2.4.56 of Apache HTTP Server.
CVE-2022-31813	9.8	0.00044	0.13323	Apache HTTP Server 2.4.53 and earlier may not send the X-Forwarded-* headers to the origin server based on client side Connection header hop-by-hop mechanism. This may be used to bypass IP based authentication on the origin server/application.
CVE-2022-23943	9.8	0.50674	0.97731	Out-of-bounds Write vulnerability in mod_sed of Apache HTTP Server allows an attacker to overwrite heap memory with possibly attacker provided data. This issue affects Apache HTTP Server 2.4 version 2.4.52 and prior versions.

Vulnerability description

Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Cookie Name	Evidence
https://bcfoodsafety.ca/wp-json/oembed/1.0/embed	PHPSESSID	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: PHPSESSID=97inf5mdm4uu5dkvh8m6rh3nl3

Vulnerability description

We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.

Recommendation

Ensure that the HttpOnly flag is set for all cookies.

Classification

CWE	CWE-1004
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Cookie Name	Evidence
https://bcfoodsafety.ca/wp-json/oembed/1.0/embed	PHPSESSID	Set-Cookie: PHPSESSID=97inf5mdm4uu5dkvh8m6rh3nl3

Vulnerability description

We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.

Recommendation

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.

Classification

CWE	CWE-614
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://bcfoodsafety.ca/wp-content/plugins/contact-form-7/includes	Found output resembling directory listing.
https://bcfoodsafety.ca/wp-content/plugins/wd-instagram-feed/booster	Found output resembling directory listing.
https://bcfoodsafety.ca/wp-content/uploads/sites/130	Found output resembling directory listing.

Vulnerability description

We noticed that the target application's web server is affected by a Directory Listing vulnerability in its URL structure. Directory listing is enabled due to misconfigured server settings, allowing attackers to view all files and subdirectories on the server.

Risk description

The risk is that it's often the case that sensitive files are "hidden" among public files in that location and attackers can use this vulnerability to access them.

Recommendation

We recommend reconfiguring the web server in order to deny directory listing. Furthermore, you should verify that there are no sensitive files at the mentioned URLs.

Classification

CWE	CWE-548
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://bcfoodsafety.ca/	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

Vulnerability description

We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.

Risk description

The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.

Recommendation

The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://bcfoodsafety.ca/	Response headers do not include the HTTP Strict-Transport-Security header

Vulnerability description

We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.

Risk description

The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).

Recommendation

The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://bcfoodsafety.ca/	Response headers do not include the X-Content-Type-Options HTTP security header

Vulnerability description

We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.

Risk description

The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.

Recommendation

We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://bcfoodsafety.ca/robots.txt

Vulnerability description

We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.

Risk description

There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.

Recommendation

We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).

Evidence

URL	Evidence
https://bcfoodsafety.ca/	Response does not include the HTTP Content-Security-Policy security header or meta tag

Vulnerability description

We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.

Risk description

The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.

Recommendation

Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://bcfoodsafety.ca/	GET	Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36	`1 : <link rel="profile" href="http://gmpg.org/xfn/11">`

Vulnerability description

We noticed that the target application is serving mixed content. This occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.

Risk description

The risk is that the insecurely loaded resources (HTTP) on an otherwise secure page (HTTPS) can be intercepted or manipulated by attackers, potentially leading to eavesdropping or content tampering.

Recommendation

Ensure that all external resources the page references are loaded using HTTPS.

Classification

CWE	CWE-311
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Animate.css	UI frameworks
Contact Form 7	WordPress plugins, Form builders
Font Awesome	Font scripts
Adobe Fonts	Font scripts
jQuery Migrate 3.4.1	JavaScript libraries
core-js 3.35.1	JavaScript libraries
Google Font API	Font scripts
GSAP	JavaScript frameworks
Apache HTTP Server 2.4.41	Web servers
Isotope	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Modernizr 2.6.2	JavaScript libraries
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
Skrollr 0.6.29	JavaScript libraries
Typekit	Font scripts
Underscore.js	JavaScript libraries
Priority Hints	Performance
WooCommerce	Ecommerce, WordPress plugins
WordPress	CMS, Blogs
WordPress Multisite	Hosting
wpBakery	Page builders, WordPress plugins
jsDelivr	CDN
Max Mega Menu	Widgets, WordPress plugins
RSS	Miscellaneous
Slider Revolution 6.6.19	Widgets, Photo galleries
Ubuntu	Operating systems
W3 Total Cache	Caching, WordPress plugins
Cart Functionality	Ecommerce
Yoast SEO 22.8	SEO, WordPress plugins

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

URL
Missing: https://bcfoodsafety.ca/.well-known/security.txt

Vulnerability description

We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.

Risk description

There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.

Recommendation

We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.

Evidence

URL	Method	Parameters	Evidence
https://bcfoodsafety.ca/wp-json/oembed/1.0/embed	GET	Query: format=xml url=https://bcfoodsafety.ca/ Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Cookies: PHPSESSID=97inf5mdm4uu5dkvh8m6rh3nl3	Possible API endpoint found at `/wp-json/oembed/1.0/embed`

Vulnerability description

We found API endpoints while crawling the given web application.

Risk description

These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.

Recommendation

Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.

Infrastructure Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	CISA KEV	Summary
CVE-2024-38476	9.8	0.01813	0.82344	No	Vulnerability in core of Apache HTTP Server 2.4.59 and earlier are vulnerably to information disclosure, SSRF or local script execution via backend applications whose response headers are malicious or exploitable. Users are recommended to upgrade to version 2.4.60, which fixes this issue.
CVE-2024-38474	9.8	0.00436	0.62288	No	Substitution encoding issue in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows attacker to execute scripts in directories permitted by the configuration but not directly reachable by any URL or source disclosure of scripts meant to only to be executed as CGI. Users are recommended to upgrade to version 2.4.60, which fixes this issue. Some RewriteRules that capture and substitute unsafely will now fail unless rewrite flag "UnsafeAllow3F" is specified.
CVE-2023-25690	9.8	0.56875	0.98028	No	Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied request-target (URL) data and is then re-inserted into the proxied request-target using variable substitution. For example, something like: RewriteEngine on RewriteRule "^/here/(.*)" "http://example.com:8080/elsewhere?$1"; [P] ProxyPassReverse /here/ http://example.com:8080/ Request splitting/smuggling could result in bypass of access controls in the proxy server, proxying unintended URLs to existing origin servers, and cache poisoning. Users are recommended to update to at least version 2.4.56 of Apache HTTP Server.
CVE-2022-31813	9.8	0.00044	0.13323	No	Apache HTTP Server 2.4.53 and earlier may not send the X-Forwarded-* headers to the origin server based on client side Connection header hop-by-hop mechanism. This may be used to bypass IP based authentication on the origin server/application.
CVE-2022-23943	9.8	0.50674	0.97731	No	Out-of-bounds Write vulnerability in mod_sed of Apache HTTP Server allows an attacker to overwrite heap memory with possibly attacker provided data. This issue affects Apache HTTP Server 2.4 version 2.4.52 and prior versions.

Vulnerability description

Vulnerabilities found for Apache HTTP Server 2.4.41

Risk description

These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed "high" severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

Recommendation

We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.

Evidence

Domain Queried	DNS Record Type	Description	Value
bcfoodsafety.ca	A	IPv4 address	159.203.191.200
bcfoodsafety.ca	NS	Name server	dns.rebel.ca
bcfoodsafety.ca	NS	Name server	dns2.rebel.ca
bcfoodsafety.ca	SOA	Start of Authority	dns.rebel.ca. noc.rebel.ca. 2025120401 10800 3600 604800 3600

Risk description

An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.

Recommendation

We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.

Operating System	Accuracy
Linux 4.15 - 5.6	100%

Evidence

Software / Version	Category
WordPress	CMS, Blogs
Slider Revolution 6.7.9	Widgets, Photo galleries
MySQL	Databases
PHP	Programming languages
Ubuntu	Operating systems
Contact Form 7	WordPress plugins, Form builders
Apache HTTP Server 2.4.41	Web servers
WordPress Multisite	Hosting
wpBakery	Page builders, WordPress plugins
W3 Total Cache	Caching, WordPress plugins
WooCommerce	Ecommerce, WordPress plugins
Yoast SEO 22.8	SEO, WordPress plugins
Typekit	Font scripts
jsDelivr	CDN
jQuery Migrate	JavaScript libraries
jQuery	JavaScript libraries
Adobe Fonts	Font scripts
Max Mega Menu	Widgets, WordPress plugins

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.