Vulnerability Scan Result

Target:

http://www.indyme.com/ (redirect)

Scanned target: https://indyme.com/

Submitted: April 17, 2025 from TJ

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	Indyme Smart Response \| Make Your Retail Stores Smarter
Description:	Indyme is the world’s leading in-store response company. Trusted by leading retailers, explore how Indyme Solutions smart technology can work for your store

IP Information

IP address	205.186.128.158
Country	US
AS number	AS398110
Net name	Godaddy LLC

Open Ports

21/tcp	ftp	ProFTPD -
25/tcp	smtp	Postfix smtpd -
53/tcp	domain	- -
80/tcp	http	nginx -
106/tcp	tcpwrapped	- -
110/tcp	pop3	Dovecot pop3d -
143/tcp	imap	Dovecot imapd -
443/tcp	https	nginx -
465/tcp	smtp	Postfix smtpd -
587/tcp	smtp	Postfix smtpd -
993/tcp	imap	Dovecot imapd -
995/tcp	pop3	Dovecot pop3d -
3306/tcp	mysql	MySQL 5.5.68-MariaDB
8443/tcp	https	sw-cp-server -

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
Amazon S3	CDN
BetterDocs	Documentation
BetterDocs plugin	WordPress plugins
jQuery CDN	CDN
Contact Form 7 6.0.6	WordPress plugins, Form builders
Bootstrap 4.5.3	UI frameworks
core-js 3.39.0	JavaScript libraries
Google Analytics UA	Analytics
Google Font API	Font scripts
imagesLoaded 5.0.0	JavaScript libraries
jQuery 3.5.1	JavaScript libraries
MySQL	Databases
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP	Programming languages
Popper	Miscellaneous
Sectigo	SSL/TLS certificate authorities
Twitter Emoji (Twemoji)	Font scripts
Unpkg	CDN
VideoJS 7.8.4	Video players
WordPress 6.8	CMS, Blogs
HubSpot WordPress plugin 11.3.5	WordPress plugins
Recent Posts Widget With Thumbnails 7.1.1	WordPress plugins
WPML 4.7.3	WordPress plugins, Translation
reCAPTCHA	Security
Google Tag Manager	Tag managers
HubSpot	Marketing automation
HubSpot Chat	Live chat
HubSpot Analytics	Analytics
jsDelivr	CDN
Plesk	Hosting panels
HSTS	Security
RSS	Miscellaneous
Yoast SEO 24.9	SEO, WordPress plugins

Web Application Vulnerabilities

Evidence

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

Evidence

URL	Evidence
https://indyme.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval().`

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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
Amazon Web Services	PaaS
Amazon S3	CDN
BetterDocs	Documentation
BetterDocs plugin	WordPress plugins
jQuery CDN	CDN
Contact Form 7 6.0.6	WordPress plugins, Form builders
Bootstrap 4.5.3	UI frameworks
core-js 3.39.0	JavaScript libraries
Google Analytics UA	Analytics
Google Font API	Font scripts
imagesLoaded 5.0.0	JavaScript libraries
jQuery 3.5.1	JavaScript libraries
MySQL	Databases
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP	Programming languages
Popper	Miscellaneous
Sectigo	SSL/TLS certificate authorities
Twitter Emoji (Twemoji)	Font scripts
Unpkg	CDN
VideoJS 7.8.4	Video players
WordPress 6.8	CMS, Blogs
HubSpot WordPress plugin 11.3.5	WordPress plugins
Recent Posts Widget With Thumbnails 7.1.1	WordPress plugins
WPML 4.7.3	WordPress plugins, Translation
reCAPTCHA	Security
Google Tag Manager	Tag managers
HubSpot	Marketing automation
HubSpot Chat	Live chat
HubSpot Analytics	Analytics
jsDelivr	CDN
Plesk	Hosting panels
HSTS	Security
RSS	Miscellaneous
Yoast SEO 24.9	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://indyme.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://indyme.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

We managed to detect a publicly accessible MySQL service.

PORT STATE SERVICE VERSION
3306/tcp open mysql MySQL 5.5.68-MariaDB

Vulnerability description

We identified that the MySQL service is publicly accessible. MySQL serves as a common database for numerous web applications and services for data storage, making it a potential prime target for determined attackers.

Risk description

The risk exists that an attacker exploits this issue by launching a password-based attack on the MySQL service. Furthermore, they could exploit zero-day vulnerabilities to obtain remote access to the MySQL database server, thereby gaining complete control over its operating system and associated services. Such an attack could lead to the exposure of confidential or sensitive information.

Recommendation

We recommend turning off public Internet access to MySQL and opting for a Virtual Private Network (VPN) that enforces two-factor authentication (2FA). Avoid enabling direct user authentication to the MySQL service via the Internet, as this could enable attackers to engage in password-guessing and potentially initiate attacks leading to complete control. However, if the MySQL service is required to be directly accessible over the Internet, we recommend reconfiguring it to be accessible only from known IP addresses.

Evidence

We managed to detect a publicly accessible File Transfer Protocol (FTP) service.

PORT STATE SERVICE VERSION
21/tcp open ftp ProFTPD

Vulnerability description

We found that the File Transfer Protocol (FTP) service is publicly accessible. The FTP enables client systems to connect to upload and download files. Nonetheless, FTP lacks encryption for the data exchanged between the server and the client, leaving all transferred data exposed in plaintext.

Risk description

Exposing this service online can enable attackers to execute man-in-the-middle attacks, capturing sensitive user credentials and the contents of files because FTP operates without encryption. The entirety of the communication between the client and the server remains unsecured in plaintext. This acquired information could further facilitate additional attacks within the network.

Recommendation

We recommend turning off FTP access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the FTP service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, utilizing SFTP (Secure File Transfer Protocol) is recommended as this protocol employs encryption to secure data transfers.

Evidence

We managed to detect a publicly accessible Post Office Protocol (POP3) service.

Starting Nmap ( https://nmap.org ) at 2025-04-17 18:36 EEST
Nmap scan report for www.indyme.com (205.186.128.158)
Host is up (0.15s latency).
rDNS record for 205.186.128.158: indyme.info

PORT    STATE SERVICE  VERSION
995/tcp open  ssl/pop3 Dovecot pop3d
|_pop3-capabilities: RESP-CODES SASL(PLAIN LOGIN DIGEST-MD5 CRAM-MD5) APOP USER UIDL PIPELINING TOP AUTH-RESP-CODE CAPA

Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 8.80 seconds

Vulnerability description

We found that the Post Office Protocol (POP3) service is publicly accessible and doesn’t include STARTTLS capability. Email clients use the Post Office Protocol (POP) to download emails for user accounts. Some POP servers are initially set up to operate over an unsecured protocol. When email clients download email content through this plaintext protocol, it can pose a substantial risk to the organization's network, especially depending on which user account is set to receive the emails.

Risk description

Exposing this service online can enable attackers to conduct man-in-the-middle attacks, thereby gaining access to sensitive user credentials and the contents of emails. Given that POP3 operates via a plaintext protocol, the entirety of the data exchanged between the client and server is left unencrypted. This critical information could then be leveraged in further attacks on the organization's network.

Recommendation

We recommend turning off POP3 access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the POP3 service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, activating STARTTLS capability (switching the connection to a secure communication) or utilizing Secure POP3 (POP3S) is recommended, as this protocol employs encryption.

Evidence

Domain Queried	DNS Record Type	Description	Value
www.indyme.com	A	IPv4 address	205.186.128.158
www.indyme.com	NS	Name server	cbru.br.ns.els-gms.att.net
www.indyme.com	NS	Name server	cmtu.mt.ns.els-gms.att.net
www.indyme.com	MX	Mail server	0 indyme-com.mail.protection.outlook.com
www.indyme.com	SOA	Start of Authority	cbru.br.ns.els-gms.att.net. rm-hostmaster.ems.att.com. 42 86400 10000 604800 86400
www.indyme.com	TXT	Text record	"google-site-verification=OUnOVp2XBEs4fpwr-dssecVIZzIT357eJBCCbg1W0Ug"
www.indyme.com	TXT	Text record	"bw=URLppHEVaLfv0pl2VSRyqS9OrRK6bTcggIfbqPo5FmUM"
www.indyme.com	TXT	Text record	"linkedin-site-verification=13ab0f34-fbf9-4852-8209-ae05567c59eb"
www.indyme.com	TXT	Text record	"atlassian-domain-verification=NSRHKt413uByFZEPJJwNbg21UPCgeVnXuvlo964nKtf22WGMzT91pP3x6lz1uyBR"
www.indyme.com	TXT	Text record	"MS=40084678E1B43E7AB0EF520105BD73CAB74393F8"
www.indyme.com	TXT	Text record	": MS=ms73434723"
www.indyme.com	TXT	Text record	"google-gws-recovery-domain-verification=49527235"
www.indyme.com	SPF	Sender Policy Framework	"v=spf1 include:spf.protection.outlook.com include:7839135.spf08.hubspotemail.net -all"
www.indyme.com	CNAME	Canonical name	indyme.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.

Domain Queried	DNS Record Type	Description	Value
www.indyme.com	SPF	Sender Policy Framework	"v=spf1 include:spf.protection.outlook.com include:7839135.spf08.hubspotemail.net -all"

Evidence

Software / Version	Category
Plesk	Hosting panels
Sentry	Issue trackers
Nginx	Web servers, Reverse proxies
React	JavaScript frameworks
RequireJS	JavaScript frameworks
Prototype	JavaScript frameworks
React Router 6	JavaScript frameworks
core-js 3.38.1	JavaScript libraries

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.