Vulnerability Scan Result

Target:

https://www.flipsnack.com/allatlanticbenefits/uhc-register-your-account

Scanned target: https://www.flipsnack.com/allatlanticbenefits/uhc-register-your-account

Submitted: Nov 18, 2025 from BH

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	UHC Register your Account by All Atlantic... - Flipsnack
Description:	Flipsnack is a digital catalog maker that makes it easy to create, publish and share html5 flipbooks. Upload a PDF or design from scratch flyers, magazines, books and more.

IP Information

ip_address	18.245.253.106
country	US
network_name	Amazon Inc
asn	AS16509

ip_address	18.245.253.13
country	US
network_name	Amazon Inc
asn	AS16509

ip_address	18.245.253.19
country	US
network_name	Amazon Inc
asn	AS16509

ip_address	18.245.253.100
country	US
network_name	Amazon Inc
asn	AS16509

Open Ports

80/tcp	http	Amazon CloudFront httpd -
443/tcp	https	CloudFront -

Web Technologies

Software / Version	Category
anime.js 3.2.1	JavaScript graphics
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Google Sign-in	Authentication
Bootstrap 4.6.1	UI frameworks
HTTP/3	Miscellaneous
jQuery 3.7.1	JavaScript libraries
Open Graph	Miscellaneous
Intercom	Live chat, CRM
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Evidence
https://www.flipsnack.com/allatlanticbenefits/uhc-register-your-account	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`script-src: script-src directive is missing. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead.`

Vulnerability description

We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.

Risk description

For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.

Recommendation

Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.

Classification

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

Evidence

Software / Version	Category
anime.js 3.2.1	JavaScript graphics
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Google Sign-in	Authentication
Bootstrap 4.6.1	UI frameworks
HTTP/3	Miscellaneous
jQuery 3.7.1	JavaScript libraries
Open Graph	Miscellaneous
Intercom	Live chat, CRM
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
https://www.flipsnack.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).

Evidence

URL
Missing: https://www.flipsnack.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.

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
www.flipsnack.com	A	IPv4 address	18.245.253.100
www.flipsnack.com	A	IPv4 address	18.245.253.19
www.flipsnack.com	A	IPv4 address	18.245.253.106
www.flipsnack.com	A	IPv4 address	18.245.253.13

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

Software / Version	Category
Google Sign-in	Authentication
Bootstrap 4.66	UI frameworks
Amazon Web Services	PaaS
HSTS	Security
Amazon CloudFront	CDN
AWS Certificate Manager	SSL/TLS certificate authorities
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.