Vulnerability Scan Result

Target:

https://9239578.app.netsuite.com/ (redirect)

Scanned target: https://9239578.app.netsuite.com/pages/customerlogin.jsp?c=9239578&whence=

Submitted: May 12, 2026 from PG

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	NetSuite - Customer Login
Description:	No description found

IP Information

ip_address	2.22.44.159
country	GB
network_name	Akamai Technologies, Inc.
asn	AS16625

Open Ports

80/tcp	http	AkamaiGHost -
443/tcp	https	AkamaiGHost -

Web Technologies

Software / Version	Category
Akamai	CDN
PWA	Miscellaneous
Akamai Bot Manager	Security
DigiCert	SSL/TLS certificate authorities
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://9239578.app.netsuite.com/pages/customerlogin.jsp	bm_sz	Set-Cookie: bm_sz=70A9995181605F104F3860A028040C31YAAQn8JkX7JoYB+eAQAAgjNxIh9S1bL9KNH2+Cm/SisR3o2007xTfEw5QWqP08Fq0yeCo/i5zGGf+6l5dTOpPRneVMZ2guZ+3aZA8IQ+v4CiWhTTCo4oHvXl5HEr2jua/OnhQvuHiEEUQcV6KgETuva87TxxIdPkvRsKR2PropKaVZ7bosaAgOiV8LFtp1/Jmb0+1OVDm90D6R2tRKtt57OF+4FZ06M7vQxWnPmf43fxkYcuqFU6lTVruBXtcKh7anE9oeByBfRLsXDXAlZ/tix518lF8ouF+6guJzSqyxfAB7KMURaeYQ4qMnOlrBdWwg9BRungS3PjKQ3HdrMm7J8TRP01Ls/ynNh/FUuLHKJY3687478~4273977

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	Cookie Name	Evidence
https://9239578.app.netsuite.com/pages/customerlogin.jsp	_abck, bm_sz	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: _abck=3282F8EF55C3D2A668D084CE2F01A6FB-1YAAQn8JkX7FoYB+eAQAAgjNxIg9jldcBYQLD8ZkS8mFOkkUXY6Q/qGJsZcBWs8n7EA+Zt1fxs4g6B7yRPStHSnWjOkAMQgAN2vvMYjeGyOJ+zfLDP+1fvMna4aezMw7vRTDH5890GGlrc3J1q8B3IwQ3bjxk1RyqYLmoALmeUImEOvKP5Q08LSCOHp6oYsoxvNPui1T0NnP1BPbsH56OVrSlD759ZV7ZmTcELfGtyESez2XQ67f4/U/Ry/mJYc8o35OSbT18z43yDp0Xr6omBtTin9J0S+1UrbFIZCMKx1bvfX/U7ZPFQj3SMU1JBguM1zWJ8MOtj9DYBO+zxhCCyvXUMRZzM9TpzXFWns2UbXppFlq5DQIq6QnsPTYj5GgdN5BPuo4AtnIZpaVx7aNTUc7BXyj9cTLpvMUajmLxrKslGOQfX8KK8DaVJ0sA53O1DB18Nm/AZXkCBQ==-1-1-1-1~~-1 Set-Cookie: bm_sz=70A9995181605F104F3860A028040C31~~YAAQn8JkX7JoYB+eAQAAgjNxIh9S1bL9KNH2+Cm/SisR3o2007xTfEw5QWqP08Fq0yeCo/i5zGGf+6l5dTOpPRneVMZ2guZ+3aZA8IQ+v4CiWhTTCo4oHvXl5HEr2jua/OnhQvuHiEEUQcV6KgETuva87TxxIdPkvRsKR2PropKaVZ7bosaAgOiV8LFtp1/Jmb0+1OVDm90D6R2tRKtt57OF+4FZ06M7vQxWnPmf43fxkYcuqFU6lTVruBXtcKh7anE9oeByBfRLsXDXAlZ/tix518lF8ouF+6guJzSqyxfAB7KMURaeYQ4qMnOlrBdWwg9BRungS3PjKQ3HdrMm7J8TRP01Ls/ynNh/FUuLHKJY~~3687478~~4273977

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://9239578.app.netsuite.com/pages/customerlogin.jsp	_abck	Set-Cookie: .netsuite.com

Vulnerability description

We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.

Risk description

The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.

Recommendation

The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`

Classification

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

Evidence

Software / Version	Category
Akamai	CDN
PWA	Miscellaneous
Akamai Bot Manager	Security
DigiCert	SSL/TLS certificate authorities
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.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://9239578.app.netsuite.com/pages/customerlogin.jsp	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. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. object-src: We recommend restricting object-src to 'none'.`

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-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://9239578.app.netsuite.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	Evidence
https://9239578.app.netsuite.com/pages/customerlogin.jsp	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

URL	Evidence
https://9239578.app.netsuite.com/pages/customerlogin.jsp	<input type="text" name="email" id="email" required data-validate-on-blur placeholder="Email address"> <input type="password" name="password" id="password" autocomplete="off" required data-validate-on-blur placeholder="Password"> <button class="login-page-form-submit" type="submit" name="submitButton" id="login-submit"> <svg width="20" height="20" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"> <path d="M11.9982 4C14.2074 4 15.9982 5.79086 15.9982 8V11H7.99823V8C7.99823 5.79086 9.78909 4 11.9982 4ZM17.9982 11V8C17.9982 4.68629 15.3119 2 11.9982 2C8.68452 2 5.99823 4.68629 5.99823 8V11H1.99823V22H21.9982V11H17.9982ZM3.99823 13H19.9982V20H3.99823V13Z"></path> </svg> <span>Log In</span> </button>

https://9239578.app.netsuite.com/pages/customerlogin.jsp

Vulnerability description

We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.

Risk description

The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.

Recommendation

Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.

Classification

CWE	CWE-287
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://9239578.app.netsuite.com/pages/customerlogin.jsp	GET	Query: c=9239578 whence= 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	Operating system paths found in the HTTP response: `/app/login/secure/enterpriselogin.nl` `/app/login/loginpage/resource.nl` `/app/login/preparepwdreset.nl`

Vulnerability description

We found operating system paths returned in a HTTP response.

Risk description

The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.

Recommendation

Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Summary
https://9239578.app.netsuite.com/pages/customerlogin.jsp?c=9239578&whence=	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET, HEAD, POST, OPTIONS` 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

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
9239578.app.netsuite.com	A	IPv4 address	2.22.44.159
9239578.app.netsuite.com	CNAME	Canonical name	app-cdn-future.na22.netsuite.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

Software / Version	Category
Akamai Bot Manager	Security
Akamai	CDN
HSTS	Security
DigiCert	SSL/TLS certificate authorities

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.