Vulnerability Scan Result

Target:

https://niqahquboolhai.com/

Scanned target: https://niqahquboolhai.com/

Submitted: April 12, 2025 from ZM

Public scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Title:

Niqah Qubool Hai | Muslim Marriage Bureau | Muslim Matrimony

Description:

A Muslims Marriage Bureau & Matrimonial Service Niqah: A Blessing from Allah - In Islam, Niqah is considered a blessing from Allah (SWT). It is mentioned several times in the Qur'an and holds utmost importance. Niqah acts as a barrier between halal and haram, and it is said that when a person gets married, they complete half of their deen. We at 'Niqah Qubool Hai' understand the importance of choosing the right one to be with you in this life and the hereafter. We help you find the one who will comple...

IP Information

IP address	104.21.64.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.16.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.80.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.96.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.112.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.32.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.48.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

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
Bootstrap 4.5.0	UI frameworks
LazySizes	JavaScript libraries, Performance
metisMenu	JavaScript libraries
Google Font API	Font scripts
HTTP/3	Miscellaneous
jQuery 3.4.1	JavaScript libraries
Moment.js 2.18.1	JavaScript libraries
Open Graph	Miscellaneous
PHP 8.2.12	Programming languages
Popper	Miscellaneous
Chart.js	JavaScript graphics
Cloudflare	CDN

Web Application Vulnerabilities

Evidence

CVSS	CVE	Summary	Affected software
9.8	CVE-2024-4577	In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, when using Apache and PHP-CGI on Windows, if the system is set up to use certain code pages, Windows may use "Best-Fit" behavior to replace characters in command line given to Win32 API functions. PHP CGI module may misinterpret those characters as PHP options, which may allow a malicious user to pass options to PHP binary being run, and thus reveal the source code of scripts, run arbitrary PHP code on the server, etc.	php 8.2.12
9.8	CVE-2024-11236	In PHP versions 8.1.* before 8.1.31, 8.2.* before 8.2.26, 8.3.* before 8.3.14, uncontrolled long string inputs to ldap_escape() function on 32-bit systems can cause an integer overflow, resulting in an out-of-bounds write.	php 8.2.12
8.8	CVE-2024-5585	In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, the fix for CVE-2024-1874 does not work if the command name includes trailing spaces. Original issue: when using proc_open() command with array syntax, due to insufficient escaping, if the arguments of the executed command are controlled by a malicious user, the user can supply arguments that would execute arbitrary commands in Windows shell.	php 8.2.12
5.9	CVE-2024-2408	The openssl_private_decrypt function in PHP, when using PKCS1 padding (OPENSSL_PKCS1_PADDING, which is the default), is vulnerable to the Marvin Attack unless it is used with an OpenSSL version that includes the changes from this pull request: https://github.com/openssl/openssl/pull/13817 (rsa_pkcs1_implicit_rejection). These changes are part of OpenSSL 3.2 and have also been backported to stable versions of various Linux distributions, as well as to the PHP builds provided for Windows since the previous release. All distributors and builders should ensure that this version is used to prevent PHP from being vulnerable. PHP Windows builds for the versions 8.1.29, 8.2.20 and 8.3.8 and above include OpenSSL patches that fix the vulnerability.	php 8.2.12
5.3	CVE-2024-5458	In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, due to a code logic error, filtering functions such as filter_var when validating URLs (FILTER_VALIDATE_URL) for certain types of URLs the function will result in invalid user information (username + password part of URLs) being treated as valid user information. This may lead to the downstream code accepting invalid URLs as valid and parsing them incorrectly.	php 8.2.12
5	CVE-2017-18214	The moment module before 2.19.3 for Node.js is prone to a regular expression denial of service via a crafted date string, a different vulnerability than CVE-2016-4055.	moment 2.18.1
5	CVE-2022-24785	Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.	moment 2.18.1
5	CVE-2022-31129	moment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a noticeable slowdown is observed with inputs above 10k characters. Users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input.	moment 2.18.1
4.3	CVE-2020-11023	In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.	jquery 3.4.1
4.3	CVE-2020-11022	In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.	jquery 3.4.1

Vulnerability description

We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1026
OWASP Top 10 - 2017	A9 - Using Components with Known Vulnerabilities
OWASP Top 10 - 2021	A6 - Vulnerable and Outdated Components

Evidence

URL	Cookie Name	Evidence
https://niqahquboolhai.com/	niqah_qubool_hai_session	Set-Cookie: niqah_qubool_hai_session=gUdeAN1aPphPfQbfqOdYe6gtyvqSWzkcdU2UyAHq

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

Evidence

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

Evidence

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

Evidence

URL	Evidence
https://niqahquboolhai.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://niqahquboolhai.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
Bootstrap 4.5.0	UI frameworks
LazySizes	JavaScript libraries, Performance
metisMenu	JavaScript libraries
Google Font API	Font scripts
HTTP/3	Miscellaneous
jQuery 3.4.1	JavaScript libraries
Moment.js 2.18.1	JavaScript libraries
Open Graph	Miscellaneous
PHP 8.2.12	Programming languages
Popper	Miscellaneous
Chart.js	JavaScript graphics
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.

Classification

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

Evidence

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

Evidence

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

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
niqahquboolhai.com	A	IPv4 address	104.21.16.1
niqahquboolhai.com	A	IPv4 address	104.21.32.1
niqahquboolhai.com	A	IPv4 address	104.21.96.1
niqahquboolhai.com	A	IPv4 address	104.21.80.1
niqahquboolhai.com	A	IPv4 address	104.21.48.1
niqahquboolhai.com	A	IPv4 address	104.21.64.1
niqahquboolhai.com	A	IPv4 address	104.21.112.1
niqahquboolhai.com	NS	Name server	bella.ns.cloudflare.com
niqahquboolhai.com	NS	Name server	ishaan.ns.cloudflare.com
niqahquboolhai.com	SOA	Start of Authority	bella.ns.cloudflare.com. dns.cloudflare.com. 2369358700 10000 2400 604800 1800
niqahquboolhai.com	AAAA	IPv6 address	2606:4700:3030::6815:1001
niqahquboolhai.com	AAAA	IPv6 address	2606:4700:3030::6815:4001
niqahquboolhai.com	AAAA	IPv6 address	2606:4700:3030::6815:6001
niqahquboolhai.com	AAAA	IPv6 address	2606:4700:3030::6815:3001
niqahquboolhai.com	AAAA	IPv6 address	2606:4700:3030::6815:5001
niqahquboolhai.com	AAAA	IPv6 address	2606:4700:3030::6815:2001
niqahquboolhai.com	AAAA	IPv6 address	2606:4700:3030::6815:7001
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issue "comodoca.com"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issue "digicert.com; cansignhttpexchanges=yes"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issue "globalsign.com"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issue "pki.goog; cansignhttpexchanges=yes"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issue "sectigo.com"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issue "ssl.com"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issuewild "comodoca.com"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issuewild "digicert.com; cansignhttpexchanges=yes"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issuewild "globalsign.com"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issuewild "letsencrypt.org"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issuewild "pki.goog; cansignhttpexchanges=yes"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issuewild "sectigo.com"
niqahquboolhai.com	CAA	Certificate Authority Authorization	0 issuewild "ssl.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.