Vulnerability Scan Result

Target:

https://sphera.com/

Scanned target: https://sphera.com/

Submitted: April 14, 2025 from NP

Public scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Title:	Sustainability Software & Operational Risk Management \| Sphera
Description:	Achieve your goals with Sphera’s end-to-end software solutions for sustainability, operational risk and EHS management.

IP Information

IP address	141.193.213.10
Country	US
AS number	AS209242
Net name	Cloudflare London LLC

IP address	141.193.213.11
Country	US
AS number	AS209242
Net name	Cloudflare London LLC

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	http	cloudflare -

Web Technologies

Software / Version	Category
jQuery Migrate 3.4.1	JavaScript libraries
HTTP/3	Miscellaneous
imagesLoaded 4.1.4	JavaScript libraries
jQuery	JavaScript libraries
MySQL	Databases
PHP	Programming languages
WordPress	CMS, Blogs
wpBakery	Page builders, WordPress plugins
WP Engine	PaaS, Hosting
WPML 4.7.3	WordPress plugins, Translation
Cloudflare	CDN
Google Tag Manager	Tag managers
Max Mega Menu	Widgets, WordPress plugins
Olark	Live chat
HSTS	Security
Yoast SEO 24.8.1	SEO, WordPress plugins

Web Application Vulnerabilities

Evidence

URL	Evidence
https://sphera.com/	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
jQuery Migrate 3.4.1	JavaScript libraries
HTTP/3	Miscellaneous
imagesLoaded 4.1.4	JavaScript libraries
jQuery	JavaScript libraries
MySQL	Databases
PHP	Programming languages
WordPress	CMS, Blogs
wpBakery	Page builders, WordPress plugins
WP Engine	PaaS, Hosting
WPML 4.7.3	WordPress plugins, Translation
Cloudflare	CDN
Google Tag Manager	Tag managers
Max Mega Menu	Widgets, WordPress plugins
Olark	Live chat
HSTS	Security
Yoast SEO 24.8.1	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.

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL
https://sphera.com/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).

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL
Missing: https://sphera.com/.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.

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.sphera.com	TXT	Text record	"v=DMARC1; p=quarantine; rua=mailto:dmarc_agg@vali.email; ruf=mailto:securityincidents@sphera.com; pct=100"

Vulnerability description

We found that the target uses p=quarantine in the DMARC policy. When a DMARC policy is set to p=quarantine, emails that fail DMARC validation are delivered but placed in the recipient’s spam or junk folder. Although it offers some protection, this policy is less strict than p=reject, which blocks such emails entirely.

Risk description

While emails failing DMARC validation are sent to the spam folder, users may still retrieve them from there, leading to a higher risk of phishing and spoofing attacks succeeding. Moreover, less strict enforcement may allow more fraudulent emails to reach user inboxes if misclassified.

Recommendation

We recommend considering moving to a stricter policy, such as p=reject, where emails that fail DMARC validation are completely rejected rather than delivered to spam folders. This reduces the risk of users interacting with potentially malicious emails.

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.sphera.com	TXT	Text record	"v=DMARC1; p=quarantine; rua=mailto:dmarc_agg@vali.email; ruf=mailto:securityincidents@sphera.com; pct=100"

Vulnerability description

We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.

Risk description

Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.

Recommendation

To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.

Evidence

Domain Queried	DNS Record Type	Description	Value
sphera.com	A	IPv4 address	141.193.213.11
sphera.com	A	IPv4 address	141.193.213.10
sphera.com	NS	Name server	pdns01.domaincontrol.com
sphera.com	NS	Name server	pdns02.domaincontrol.com
sphera.com	MX	Mail server	10 sphera-com.mail.protection.outlook.com
sphera.com	MX	Mail server	100 mail1.sphera.com
sphera.com	MX	Mail server	100 mail2.sphera.com
sphera.com	MX	Mail server	100 mail3.sphera.com
sphera.com	SOA	Start of Authority	pdns01.domaincontrol.com. dns.jomax.net. 2025032105 28800 7200 604800 600
sphera.com	TXT	Text record	"asv=bd97dc147c5bfc2c95fb8a5713525abb"
sphera.com	TXT	Text record	"atlassian-domain-verification=fOGfV9xyCKr649lTZf2r/8nEfWTb6bUrejOhNx1noOAYJttGtv7e00/zBQHCk2L1"
sphera.com	TXT	Text record	"pardot272282=de4a3f0a610e2ec19f28c67ead9f3ba84a956b3d03e5d9fca5d2bf7ba1e3ae8c"
sphera.com	TXT	Text record	"google-site-verification=HbYTyQCQda1lR3Fc30D-8ruTo3T1w_E5NiphaBxs14w"
sphera.com	TXT	Text record	"docker-verification=2a66754d-d0f9-4e8f-b078-88faa800f93d"
sphera.com	TXT	Text record	"adobe-idp-site-verification=11f30884e7633f01bf42f956531584e23f28fb31aa01715a70c8c3c600e70049"
sphera.com	TXT	Text record	"oodv0cfm2tdo4nl0lo3c9es23u"
sphera.com	TXT	Text record	"hes=6bbccdb941045db5ac4d691fabdccda8"
sphera.com	TXT	Text record	"MS=ms51508909"
sphera.com	TXT	Text record	"vp9cdpth115fdb6mkr8rcmi85q"
sphera.com	TXT	Text record	"teamviewer-sso-verification=71a3204c2d634dbca8401a670abb0e66"
sphera.com	TXT	Text record	"docusign=dfd3635f-ef2f-43c1-97d3-6f7d3216e33b"
sphera.com	TXT	Text record	"box-domain-verification=3a6b361c5458c73c84eaaa293726541efa9c70fb1c518638bb6d110f01e897db"
sphera.com	SPF	Sender Policy Framework	"v=spf1 include:mail.zendesk.com include:spf.protection.outlook.com include:sendgrid.net include:aspmx.pardot.com include:mailsenders.netsuite.com include:_spfaponly.accessplanit.com ip4:192.184.127.206 ip4:192.184.127.207 ip4:192.184.127.231 ip4:192.184.1" "27.211 ip4:20.37.137.251 ip4:20.37.138.65 ip4:20.90.247.120 ip4:40.81.158.122 ip4:40.81.158.243 ip4:51.145.122.92 ip4:20.184.62.32 ip4:52.158.210.83 ip4:40.65.174.19 ip4:80.79.134.253 -all"
_dmarc.sphera.com	TXT	Text record	"v=DMARC1; p=quarantine; rua=mailto:dmarc_agg@vali.email; ruf=mailto:securityincidents@sphera.com; pct=100"

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.

Evidence

Domain Queried	DNS Record Type	Description	Value
sphera.com	SPF	Sender Policy Framework	"v=spf1 include:mail.zendesk.com include:spf.protection.outlook.com include:sendgrid.net include:aspmx.pardot.com include:mailsenders.netsuite.com include:_spfaponly.accessplanit.com ip4:192.184.127.206 ip4:192.184.127.207 ip4:192.184.127.231 ip4:192.184.1" "27.211 ip4:20.37.137.251 ip4:20.37.138.65 ip4:20.90.247.120 ip4:40.81.158.122 ip4:40.81.158.243 ip4:51.145.122.92 ip4:20.184.62.32 ip4:52.158.210.83 ip4:40.65.174.19 ip4:80.79.134.253 -all"

Evidence

DKIM selector	Key type	Key size	Value
200608	rsa	1296	"k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGoQCNwAQdJBy23MrShs1EuHqK/dtDC33QrTqgWd9CJmtM3CK2ZiTYugkhcxnkEtGbzg+IJqcDRNkZHyoRezTf6QbinBB2dbyANEuwKI5DVRBFowQOj9zvM3IvxAEboMlb0szUjAoML94HOkKuGuCkdZ1gbVEi3GcVwrIQphal1QIDAQAB;"
s2	rsa	1296	"k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD1ekQhDGVScqHtOC/cPLp32PCPtaZd3n8AUONvjZQergT4FWvnV9iEEG3CE8rl2aO7JJYbsK0d5uWrWfYkZNhIIhBYz85hGBnhAVMgebmnNoOeNF63jOXCla94xxRnlaqOWfgQ4lYvVS/ZONL5edchaSDALevgu4+Siof5jko2wQIDAQAB"
s1	rsa	1446	"k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuWROhiWPlcujlnuUbdpkN85uUG3dkcdygEM7p54wRlc6ivDqpNazByVvacbuo13BHhScGUF6x3aBHmNSKRDhPtQw6NPEClV/QN85lQOHAJhcCzEHKYQ1luQwjhPVech5PVEc7MaQbwWPdMWl4hzM13CtMeLqpCSjemQ7SwkGDTkx0JnBlR5Hfj8hk+yUE6mqB8oQw" "vSX92euhXzI8nv4dH7Gw0Sh9nXKpdH+ok+kebcK7+F/HrVMkcc1rLqM5qCcSqpEaC9pHS7XNaDQ+zhrjuhYcki6LISYVkCNfUoKoYhSmG0U4/1cCPMFC3HNtpCoGZncwHxmmE004YSjnWHK/wIDAQAB"
selector1	rsa	1296	"v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC9tMFNJMoLz1GngrhdTZpD0/7nbWs9IXwEDB07MJ1QKw+QbSPp0NLrq+pBzwa7U1Vv8OUpM5vuyWOqoW0UD6aEVzlM/oYtE2VGW4cjlvD9hzHqzIYkiCN0lOr8U9nD8oukJdFX7oMy8ZNaQWNhxTfudfaqeEwf7KdeOH9juyV68QIDAQAB;"

Evidence

Software / Version	Category
Cloudflare	CDN
HTTP/3	Miscellaneous

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

Software / Version	Category
Cloudflare	CDN
HTTP/3	Miscellaneous

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

Software / Version	Category
Cloudflare	CDN

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.