Vulnerability Scan Result

Target:

https://expediataap.cn/ (redirect)

Scanned target: https://www.expediataap.cn/

Submitted: Mar 22, 2026 from SV

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Expedia Taap \| 旅行社联盟计划
Description:	通过 Expedia TAAP，旅行顾问可以获得海量优质旅行产品和一流的预订体验，从而为他们实现收益最大化。

IP Information

ip_address	2.22.248.182
country	IT
network_name	Akamai International B.V.
asn	AS20940

ip_address	2.22.248.160
country	IT
network_name	Akamai International B.V.
asn	AS20940

Open Ports

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

Web Technologies

Software / Version	Category
Akamai	CDN
Adobe Experience Platform Identity Service	Customer data platform
Hammer.js 2.0.4	JavaScript libraries
Handlebars 4.0.5	JavaScript frameworks
Java	Programming languages
jQuery 3.2.1	JavaScript libraries
Modernizr 2.8.3	JavaScript libraries
Adobe Analytics	Analytics
Akamai Bot Manager	Security
Envoy	Reverse proxies
reCAPTCHA	Security
HSTS	Security
ServiceNow	Miscellaneous
JSP	Web frameworks
Zipkin	Analytics

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2019-19919	9.8	0.17796	0.95061	Versions of handlebars prior to 4.3.0 are vulnerable to Prototype Pollution leading to Remote Code Execution. Templates may alter an Object's __proto__ and __defineGetter__ properties, which may allow an attacker to execute arbitrary code through crafted payloads.

Vulnerability description

Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.

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. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

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

Evidence

URL	Cookie Name	Evidence
https://www.expediataap.cn/	tpid	Set-Cookie: .expediataap.cn

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

URL	Cookie Name	Evidence
https://www.expediataap.cn/	tpid, iEAPID, linfo, cesc, HMS	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: tpid=v.1,5208 Set-Cookie: iEAPID=70975 Set-Cookie: linfo=v.4,\|0\|0\|255\|1\|0\|\|\|\|\|\|\|\|2052\|0\|0\|\|0\|0\|0\|-1\|-1 Set-Cookie: cesc=%7B%22lpe%22%3A%5B%22efd5c504-b9fa-4f3b-8f9a-9515f2570e3f%22%2C1774154583978%5D%2C%22marketingClick%22%3A%5B%22true%22%2C1774154583978%5D%2C%22lmc%22%3A%5B%22DIRECT.WEB_HOME%22%2C1774154583978%5D%2C%22hitNumber%22%3A%5B%221%22%2C1774154583978%5D%2C%22amc%22%3A%5B%22DIRECT.WEB_HOME%22%2C1774154583978%5D%2C%22visitNumber%22%3A%5B%221%22%2C1774154583978%5D%2C%22ape%22%3A%5B%22efd5c504-b9fa-4f3b-8f9a-9515f2570e3f%22%2C1774154583978%5D%2C%22cidVisit%22%3A%5B%22Brand.DTI%22%2C1774154583978%5D%2C%22entryPage%22%3A%5B%22Homepage%22%2C1774154583978%5D%2C%22cid%22%3A%5B%22Brand.DTI%22%2C1774154583978%5D%7D Set-Cookie: HMS=db0c00f9-4d01-3965-abb5-49349f8dfa26

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

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2020-11023	6.9	0.36851	0.97102	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.
CVE-2020-11022	6.9	0.03166	0.86821	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.
CVE-2019-11358	6.1	0.02646	0.85579	jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.

Vulnerability description

Risk description

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

Evidence

Software / Version	Category
Akamai	CDN
Adobe Experience Platform Identity Service	Customer data platform
Hammer.js 2.0.4	JavaScript libraries
Handlebars 4.0.5	JavaScript frameworks
Java	Programming languages
jQuery 3.2.1	JavaScript libraries
Modernizr 2.8.3	JavaScript libraries
Adobe Analytics	Analytics
Akamai Bot Manager	Security
Envoy	Reverse proxies
reCAPTCHA	Security
HSTS	Security
ServiceNow	Miscellaneous
JSP	Web frameworks
Zipkin	Analytics

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://www.expediataap.cn/	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://www.expediataap.cn/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'.`

https://www.expediataap.cn/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'.

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 Evidence

URL	Evidence
https://www.expediataap.cn/taap/signin	<input type="text" id="taapSigninEmailAddress" name="email" aria-describedby="taap_email_address_error" data-validation-msg="邮箱地址无效。" class=" input_fields" autocomplete="off" aria-required="true"> <input type="password" id="taapSigninPassword" name="taap_signin_password" aria-describedby="taap_signin_password_error" data-validation-msg="密码无效。" class=" input_fields" autocomplete="off" aria-required="true"> <button type="submit" class="btn-primary btn-action" id="submit-signin-button"><span class="btn-label">登录</span></button>

https://www.expediataap.cn/taap/signin

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://www.expediataap.cn/taap/signin	GET	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 Cookies: CRQS=t\|5208`s\|1070975`l\|zh_CN`c\|CNY CRQSS=e\|70975 DUAID=4da9efe4-71bd-4fbc-862e-559e1435d809 EG_SESSIONTOKEN=ClAKJgokYmYzMzEwZGUtMzgyNi00Mzc0L...	Email Address: accountmanagement@expediataap.cn

Vulnerability description

We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.

Risk description

The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.

Recommendation

Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.

Classification

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

Infrastructure Vulnerabilities

Evidence

We managed to detect that Linux 5.4 has reached the End-of-Life (EOL).

Version detected: 5.4 End-of-life date: 2025-12-03 Latest version for the cycle: 5.4.302 This release cycle (5.4) does have long-term-support (LTS). The cycle was released on 2019-11-25 and its latest release date was 2025-12-03.

Risk description

Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.

Recommendation

To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.

Evidence

Software / Version	Category
Envoy	Reverse proxies
Akamai	CDN
Akamai Bot Manager	Security
reCAPTCHA	Security
Zipkin	Analytics
HSTS	Security
Loadable-Components	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

Domain Queried	DNS Record Type	Description	Value
www.expediataap.cn	A	IPv4 address	2.18.254.185
www.expediataap.cn	A	IPv4 address	95.101.181.125
www.expediataap.cn	AAAA	IPv6 address	2a02:26f0:8d00:14::213:7c98
www.expediataap.cn	AAAA	IPv6 address	2a02:26f0:8d00:14::213:7c97
www.expediataap.cn	CNAME	Canonical name	wwwexpediataapcn.dv.edgekey.net

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
Envoy	Reverse proxies
Akamai	CDN
Akamai Bot Manager	Security
reCAPTCHA	Security
Zipkin	Analytics
HSTS	Security
Loadable-Components	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.