Vulnerability Scan Result

Target:

https://www.sealbill.app/ (redirect)

Scanned target: https://sealbill.app/lv

Submitted: Feb 16, 2026 from KP

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Rēķinu automatizācija interešu izglītībai, pulciņiem un sporta nodarbībām \| SealBill – SealBill
Description:	Rēķinu izrakstīšana, maksājumu kontrole un automātiski atgādinājumi interešu izglītības un sporta nodarbībām – SealBill.

IP Information

ip_address	104.21.11.94
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	172.67.148.153
country	-
network_name	Cloudflare, Inc.
asn	AS13335

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
2082/tcp	http	Cloudflare http proxy -
2083/tcp	https	nginx -
2086/tcp	http	Cloudflare http proxy -
2087/tcp	https	nginx -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	http	cloudflare -

Web Technologies

Software / Version	Category
Bootstrap 5.3.3	UI frameworks
core-js 3.6.5	JavaScript libraries
Google Font API	Font scripts
HTTP/3	Miscellaneous
Open Graph	Miscellaneous
Vue.js	JavaScript frameworks
PWA	Miscellaneous
Cloudflare	CDN
jsDelivr	CDN
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Evidence
https://sealbill.app/lv	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	Evidence
https://sealbill.app/lv/_contact	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
https://sealbill.app/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://sealbill.app/lv	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

Software / Version	Category
Bootstrap 5.3.3	UI frameworks
core-js 3.6.5	JavaScript libraries
Google Font API	Font scripts
HTTP/3	Miscellaneous
Open Graph	Miscellaneous
Vue.js	JavaScript frameworks
PWA	Miscellaneous
Cloudflare	CDN
jsDelivr	CDN
HSTS	Security

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	Evidence
https://sealbill.app/lv	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	Summary
https://sealbill.app/lv	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,HEAD` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

CWE	CWE-16
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://sealbill.app/.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.

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.sealbill.app	TXT	Text record	"v=DMARC1; p=quarantine; pct=100; fo=1; ri=3600; adkim=r; aspf=r; rua=mailto:de2f0fc8@dmarc.mailgun.org,mailto:416b4983@inbox.ondmarc.com,mailto:dmarc_rua@onsecureserver.net; ruf=mailto:de2f0fc8@dmarc.mailgun.org,mailto:416b4983@inbox.ondmarc.com;"

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.sealbill.app	TXT	Text record	"v=DMARC1; p=quarantine; pct=100; fo=1; ri=3600; adkim=r; aspf=r; rua=mailto:de2f0fc8@dmarc.mailgun.org,mailto:416b4983@inbox.ondmarc.com,mailto:dmarc_rua@onsecureserver.net; ruf=mailto:de2f0fc8@dmarc.mailgun.org,mailto:416b4983@inbox.ondmarc.com;"

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
sealbill.app	SPF	Sender Policy Framework	"v=spf1 include:mailgun.org include:_spf.google.com ~all"

Vulnerability description

We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.

Risk description

The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.

Recommendation

We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.

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.

Operating System	Accuracy
FreeBSD 11.0-RELEASE	91%

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.

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.

Evidence

Software / Version	Category
Bootstrap 5.3.3	UI frameworks
Vue.js	JavaScript frameworks
jsDelivr	CDN
HSTS	Security
Cloudflare	CDN
HTTP/3	Miscellaneous
Google Font API	Font scripts
PWA	Miscellaneous
Open Graph	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

Domain Queried	DNS Record Type	Description	Value
sealbill.app	A	IPv4 address	104.21.11.94
sealbill.app	A	IPv4 address	172.67.148.153
sealbill.app	NS	Name server	maciej.ns.cloudflare.com
sealbill.app	NS	Name server	ulla.ns.cloudflare.com
sealbill.app	MX	Mail server	1 aspmx.l.google.com
sealbill.app	MX	Mail server	10 alt3.aspmx.l.google.com
sealbill.app	MX	Mail server	10 alt4.aspmx.l.google.com
sealbill.app	MX	Mail server	5 alt1.aspmx.l.google.com
sealbill.app	MX	Mail server	5 alt2.aspmx.l.google.com
sealbill.app	SOA	Start of Authority	maciej.ns.cloudflare.com. dns.cloudflare.com. 2396717897 10000 2400 604800 1800
sealbill.app	AAAA	IPv6 address	2606:4700:3031::ac43:9499
sealbill.app	AAAA	IPv6 address	2606:4700:3036::6815:b5e
sealbill.app	SPF	Sender Policy Framework	"v=spf1 include:mailgun.org include:_spf.google.com ~all"
_dmarc.sealbill.app	TXT	Text record	"v=DMARC1; p=quarantine; pct=100; fo=1; ri=3600; adkim=r; aspf=r; rua=mailto:de2f0fc8@dmarc.mailgun.org,mailto:416b4983@inbox.ondmarc.com,mailto:dmarc_rua@onsecureserver.net; ruf=mailto:de2f0fc8@dmarc.mailgun.org,mailto:416b4983@inbox.ondmarc.com;"

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

DKIM selector	Key type	Key size	Value
google	rsa	1422	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzIo0fi5bmQDx9PDVxrHQPYViSOAwYy0YhzD+IHTUKrYHkqlAiqp4jx9K/sfEYFkgt2JEDzKNJn4OchafEls1nYQf/KSaZuZ8wRFzAk3NRVW2QdNe2OH/sQZWc0eF+lhiXVrlA2EbPtMU3nCGfTxu5DFLphL+v4RLgbXtR98i9tRKlR1o2YFYxU7jeyJIdBQ7z" "dPaZ6sp2yXxA3xvs0ftn/ePc69Kouvmp4LEEhpLBomtAQJP70zx7eEEFW8D/qVo2usGezs6+qbM0dxjHixLKvS79Y+9JCVH9M3JvrOaR/wkVujVbRmL99oUd4tR51IS4Go+1Fu7jSvhKZ4qfb2nbwIDAQAB"