Vulnerability Scan Result

Target:

http://aerecruitment.ae/ (redirect)

Scanned target: https://aerecruitment.ae/

Submitted: Nov 02, 2025 from KZ

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	AE Recruitment - Architectural and Design Jobs in the Middle East
Description:	Discover AE Recruitment, the architecture and design recruitment consultancy connecting elite architects and designers with visionary firms.

IP Information

ip_address	162.159.137.54
country	-
network_name	Cloudflare Inc
asn	AS13335

ip_address	162.159.136.54
country	-
network_name	Cloudflare Inc
asn	AS13335

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	Cloudflare http proxy -
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	https	Cloudflare http proxy -

Web Technologies

Software / Version	Category
Elementor 3.32.4	Page builders, WordPress plugins
Font Awesome	Font scripts
jQuery Migrate 3.4.1	JavaScript libraries
core-js 3.43.0	JavaScript libraries
Google Analytics	Analytics
Google Font API	Font scripts
HTTP/3	Miscellaneous
imagesLoaded 5.0.0	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
MySQL	Databases
New Relic	RUM
Open Graph	Miscellaneous
Google Pay	Payment processors
PHP	Programming languages
Stripe 3	Payment processors
Swiper	JavaScript libraries
Priority Hints	Performance
WooCommerce 10.2.2	Ecommerce, WordPress plugins
WordPress 6.8.3	CMS, Blogs
WP Rocket	Caching, WordPress plugins
Astra 4.11.13	WordPress themes
Cloudflare	CDN
Cloudflare Bot Management	Security
Google Tag Manager	Tag managers
LearnDash 4.25.3	LMS, WordPress plugins
MonsterInsights 9.9.0	WordPress plugins, Analytics
RSS	Miscellaneous
Yoast SEO 26.1.1	SEO, WordPress plugins

Web Application Vulnerabilities

Evidence

Software / Version	Category
Elementor 3.32.4	Page builders, WordPress plugins
Font Awesome	Font scripts
jQuery Migrate 3.4.1	JavaScript libraries
core-js 3.43.0	JavaScript libraries
Google Analytics	Analytics
Google Font API	Font scripts
HTTP/3	Miscellaneous
imagesLoaded 5.0.0	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
MySQL	Databases
New Relic	RUM
Open Graph	Miscellaneous
Google Pay	Payment processors
PHP	Programming languages
Stripe 3	Payment processors
Swiper	JavaScript libraries
Priority Hints	Performance
WooCommerce 10.2.2	Ecommerce, WordPress plugins
WordPress 6.8.3	CMS, Blogs
WP Rocket	Caching, WordPress plugins
Astra 4.11.13	WordPress themes
Cloudflare	CDN
Cloudflare Bot Management	Security
Google Tag Manager	Tag managers
LearnDash 4.25.3	LMS, WordPress plugins
MonsterInsights 9.9.0	WordPress plugins, Analytics
RSS	Miscellaneous
Yoast SEO 26.1.1	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.

Evidence

URL	Evidence
https://aerecruitment.ae/	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
https://aerecruitment.ae/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://aerecruitment.ae/	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://aerecruitment.ae/	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
https://aerecruitment.ae/	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
Missing: https://aerecruitment.ae/.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.aerecruitment.ae	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:d5d0edb7@mxtoolbox.dmarc-report.com; ruf=mailto:d5d0edb7@forensics.dmarc-report.com; fo=1"

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

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
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.

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
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.

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
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.

Evidence

Software / Version	Category
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Stripe	Payment processors
Google Pay	Payment processors
Google Analytics	Analytics
Cloudflare Bot Management	Security
Cloudflare	CDN
HTTP/3	Miscellaneous
Astra 4.11.13	WordPress themes
WP Rocket	Caching, WordPress plugins
WooCommerce 10.2.2	Ecommerce, WordPress plugins
LearnDash 4.25.3	LMS, WordPress plugins
Elementor 3.32.4	Page builders, WordPress plugins
Yoast SEO	SEO, WordPress plugins
MonsterInsights 9.9.0	WordPress plugins, Analytics
jQuery Migrate 3.4.1	JavaScript libraries
jQuery	JavaScript libraries
Google Tag Manager	Tag managers
Font Awesome	Font scripts
Priority Hints	Performance
Google Font API	Font scripts
RSS	Miscellaneous
Open Graph	Miscellaneous
imagesLoaded 5.0.0	JavaScript libraries
New Relic	RUM
jQuery UI 1.13.3	JavaScript libraries
core-js 3.38.1	JavaScript libraries
Swiper	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.

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
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.

Evidence

DKIM selector	Key type	Key size	Value
s1	rsa	1296	"v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCmupyvj1YP8BWBXbOUxu22JhVuP22EsAX5kK0I09q5Zpw5utvpwUDnqbFE3pfqIBagFNzquLTORD6PyteE0/dbJ2blGJth/Rs5Ox5RW7V33uRjaUyD7mKGqvbmhf/akc1vc+bq9D2EJdSGG2JeNxFEdmdNnkSawcGDmNqY3PFFrQIDAQAB;"
selector1	rsa	1296	"v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCmupyvj1YP8BWBXbOUxu22JhVuP22EsAX5kK0I09q5Zpw5utvpwUDnqbFE3pfqIBagFNzquLTORD6PyteE0/dbJ2blGJth/Rs5Ox5RW7V33uRjaUyD7mKGqvbmhf/akc1vc+bq9D2EJdSGG2JeNxFEdmdNnkSawcGDmNqY3PFFrQIDAQAB;"

Operating System	Accuracy
FreeBSD 11.0-RELEASE	91%

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
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.

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
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.

Evidence

Domain Queried	DNS Record Type	Description	Value
aerecruitment.ae	A	IPv4 address	162.159.137.54
aerecruitment.ae	A	IPv4 address	162.159.136.54
aerecruitment.ae	NS	Name server	ns4.bdm.microsoftonline.com
aerecruitment.ae	NS	Name server	ns3.bdm.microsoftonline.com
aerecruitment.ae	NS	Name server	ns1.bdm.microsoftonline.com
aerecruitment.ae	NS	Name server	ns2.bdm.microsoftonline.com
aerecruitment.ae	MX	Mail server	0 aerecruitment-ae.mail.protection.outlook.com
aerecruitment.ae	SOA	Start of Authority	ns1.bdm.microsoftonline.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300
aerecruitment.ae	TXT	Text record	"mscid=j1nRDcat6sy7FGLzrlQRliGHzO548vw9hahBLBflD08hJlOfBGZz+IY0iz1flOdCY7wpYhm/lejcEggpWOWhlw=="
aerecruitment.ae	TXT	Text record	"zoho-verification=zb21964920.zmverify.zoho.eu"
aerecruitment.ae	TXT	Text record	"k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv+s0CAnXXRkHIUydcdr+Om2ADvzpa2Zs0zFqv48xS0rOHxop9mOjk1MrE7wW0/RLk8MVJul2Ce36OBQbZ1PXgp5OqQwQfOnrMVowiz9sd1a/cqSrDMwTDaIK8RQVi1GQxvBncHJuT3DVVrhz2Z0sDSRM0I+eKwdVhG7E1Ghda0FBtVblrKs27vK9I6RhcVwLJCbDtx/BSUt" " 2QJuXwyc41MkLGAUBSwOB4KxmXMkQ8Otu7tUQm/cP6AntfGNcRQW9atbvs80ZuEbc7q0YdFhIIhhQd47bIwrX9ouWwo5T7f4fOvPvM70AfLlb00gjopYP77FUenx9jVW7TnI0gVmHRQIDAQAB"
aerecruitment.ae	TXT	Text record	"facebook-domain-verification=cbeax3a2hkzbtys95c0sbzwbhfkdoq"
aerecruitment.ae	TXT	Text record	"stripe-verification=a9befdbfe45518eeb270024042e89e2cd0da262f02468bacf7d14d1333450f7e"
aerecruitment.ae	TXT	Text record	"ca3-1e89672aec70475395eda36d7550c185"
aerecruitment.ae	TXT	Text record	"k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGdBkq/U2wzVoRPAPZUOUcK400iHwZojrKM680LCHjt5t/kmrmbZ/tBp7Z2KU6T4pseIO9qYU7JYKsjzQ0qJ30W4/QqqZ8q5g8AAyNSWFARDunRmvFu6EfJLnXQudHQ9e3As80GVdXL1WFPxv87Fl/2bxil95V5JLG78Jj1E1ajwIDAQAB"
aerecruitment.ae	SPF	Sender Policy Framework	"v=spf1 include:spf.protection.outlook.com -all"
_dmarc.aerecruitment.ae	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:d5d0edb7@mxtoolbox.dmarc-report.com; ruf=mailto:d5d0edb7@forensics.dmarc-report.com; fo=1"

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.