ZAP Scanning Report

The identified library appears to be vulnerable.

The identified library axios, version 1.6.8 is vulnerable.

CVE-2025-62718

CVE-2025-27152

CVE-2024-39338

CVE-2025-58754

CVE-2026-42041

CVE-2026-42040

CVE-2026-25639

CVE-2026-39865

CVE-2026-42039

CVE-2026-42034

CVE-2026-40175

CVE-2026-42033

CVE-2026-42044

CVE-2026-42264

CVE-2026-42043

CVE-2026-42042

CVE-2026-42038

CVE-2026-42037

CVE-2026-42036

CVE-2026-42035

https://github.com/axios/axios/issues/6463

https://github.com/axios/axios/security/advisories/GHSA-vf2m-468p-8v99

https://github.com/axios/axios/security/advisories/GHSA-xhjh-pmcv-23jw

https://github.com/axios/axios/commit/28c721588c7a77e7503d0a434e016f852c597b57

https://github.com/axios/axios/pull/10661

https://github.com/axios/axios/pull/10660

https://github.com/axios/axios/commit/fb3befb6daac6cad26b2e54094d0f2d9e47f24df

https://github.com/axios/axios/releases/tag/v1.12.0

https://github.com/axios/axios/security/advisories/GHSA-pmwg-cvhr-8vh7

https://github.com/axios/axios/pull/7369

https://github.com/axios/axios/security/advisories/GHSA-43fc-jf86-j433

https://github.com/axios/axios/releases

https://github.com/axios/axios/releases/tag/v1.8.2

https://github.com/axios/axios/security/advisories/GHSA-3p68-rc4w-qgx5

https://github.com/axios/axios/security/advisories/GHSA-62hf-57xw-28j9

https://github.com/axios/axios/security/advisories/GHSA-m7pr-hjqh-92cm

https://github.com/axios/axios/security/advisories/GHSA-q8qp-cvcw-x6jj

https://github.com/advisories/GHSA-8hc4-vh64-cxmj

https://github.com/axios/axios/commit/945435fc51467303768202250debb8d4ae892593

https://github.com/axios/axios/security/advisories/GHSA-3w6x-2g7m-8v23

https://github.com/axios/axios/releases/tag/v1.13.5

https://github.com/axios/axios/security/advisories/GHSA-6chq-wfr3-2hj9

https://github.com/axios/axios/commit/6b6b605eaf73852fb2dae033f1e786155959de3a

https://github.com/axios/axios/releases/tag/v0.30.3

https://github.com/axios/axios/commit/fb8eec214ce7744b5ca787f2c3b8339b2f54b00f

https://github.com/axios/axios/pull/6543

https://jeffhacks.com/advisories/2024/06/24/CVE-2024-39338.html

https://github.com/axios/axios/security/advisories/GHSA-fvcv-3m26-pcqx

https://github.com/axios/axios/security/advisories/GHSA-qj83-cq47-w5f8

https://github.com/axios/axios/pull/6539

https://datatracker.ietf.org/doc/html/rfc3986#section-3.2.2

https://github.com/axios/axios/security/advisories/GHSA-445q-vr5w-6q77

https://github.com/axios/axios/commit/d7ff1409c68168d3057fc3891f911b2b92616f9e

https://github.com/advisories/GHSA-jr5f-v2jv-69x6

https://github.com/axios/axios/pull/7388

https://github.com/axios/axios/releases/tag/v1.13.2

https://github.com/axios/axios/releases/tag/v1.15.0

https://github.com/axios/axios/releases/tag/v1.7.4

https://github.com/axios/axios/security/advisories/GHSA-4hjh-wcwx-xvwj

https://datatracker.ietf.org/doc/html/rfc1034#section-3.1

https://nvd.nist.gov/vuln/detail/CVE-2024-39338

https://github.com/axios/axios

https://github.com/axios/axios/security/advisories/GHSA-5c9x-8gcm-mpgx

https://github.com/axios/axios/security/advisories/GHSA-pf86-5x62-jrwf

https://github.com/axios/axios/security/advisories/GHSA-w9j2-pvgh-6h63

https://github.com/axios/axios/security/advisories/GHSA-jr5f-v2jv-69x6

https://github.com/axios/axios/commit/363185461b90b1b78845dc8a99a1f103d9b122a1

https://nvd.nist.gov/vuln/detail/CVE-2025-27152

https://github.com/axios/axios/pull/7011

https://github.com/axios/axios/security/advisories/GHSA-xx6v-rp6x-q39c

Upgrade to the latest version of the affected library.

Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.

Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.

The response does not protect against 'ClickJacking' attacks. It should include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options.

Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.

If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's "frame-ancestors" directive.

The integrity attribute is missing on a script or link tag served by an external server. The integrity tag prevents an attacker who have gained access to this server from injecting a malicious content.

Provide a valid integrity attribute to the tag.

The page includes one or more script files from a third-party domain.

Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.

Cross-Origin-Embedder-Policy header is a response header that prevents a document from loading any cross-origin resources that don't explicitly grant the document permission (using CORP or CORS).

Ensure that the application/web server sets the Cross-Origin-Embedder-Policy header appropriately, and that it sets the Cross-Origin-Embedder-Policy header to 'require-corp' for documents.

If possible, ensure that the end user uses a standards-compliant and modern web browser that supports the Cross-Origin-Embedder-Policy header (https://caniuse.com/mdn-http_headers_cross-origin-embedder-policy).

Cross-Origin-Opener-Policy header is a response header that allows a site to control if others included documents share the same browsing context. Sharing the same browsing context with untrusted documents might lead to data leak.

Ensure that the application/web server sets the Cross-Origin-Opener-Policy header appropriately, and that it sets the Cross-Origin-Opener-Policy header to 'same-origin' for documents.

'same-origin-allow-popups' is considered as less secured and should be avoided.

If possible, ensure that the end user uses a standards-compliant and modern web browser that supports the Cross-Origin-Opener-Policy header (https://caniuse.com/mdn-http_headers_cross-origin-opener-policy).

Cross-Origin-Resource-Policy header is an opt-in header designed to counter side-channels attacks like Spectre. Resource should be specifically set as shareable amongst different origins.

Ensure that the application/web server sets the Cross-Origin-Resource-Policy header appropriately, and that it sets the Cross-Origin-Resource-Policy header to 'same-origin' for all web pages.

'same-site' is considered as less secured and should be avoided.

If resources must be shared, set the header to 'cross-origin'.

If possible, ensure that the end user uses a standards-compliant and modern web browser that supports the Cross-Origin-Resource-Policy header (https://caniuse.com/mdn-http_headers_cross-origin-resource-policy).

Permissions Policy Header is an added layer of security that helps to restrict from unauthorized access or usage of browser/client features by web resources. This policy ensures the user privacy by limiting or specifying the features of the browsers can be used by the web resources. Permissions Policy provides a set of standard HTTP headers that allow website owners to limit which features of browsers can be used by the page such as camera, microphone, location, full screen etc.

Ensure that your web server, application server, load balancer, etc. is configured to set the Permissions-Policy header.

A timestamp was disclosed by the application/web server. - Unix

1521486534, which evaluates to: 2018-03-19 19:08:54.

1541459225, which evaluates to: 2018-11-05 23:07:05.

1694144372, which evaluates to: 2023-09-08 03:39:32.

1779033703, which evaluates to: 2026-05-17 16:01:43.

1899447441, which evaluates to: 2030-03-11 08:17:21.

Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.

The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.

This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.

At "High" threshold this scan rule will not alert on client or server error responses.

This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.

At "High" threshold this scan rule will not alert on client or server error responses.

This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.

At "High" threshold this scan rule will not alert on client or server error responses.

This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.

At "High" threshold this scan rule will not alert on client or server error responses.

This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.

At "High" threshold this scan rule will not alert on client or server error responses.

Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.

If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.

The application appears to be a modern web application. If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one.

No links have been found while there are scripts, which is an indication that this is a modern web application.

No links have been found while there are scripts, which is an indication that this is a modern web application.

No links have been found while there are scripts, which is an indication that this is a modern web application.

This is an informational alert and so no changes are required.

The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.

For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".

The response contents are storable by caching components such as proxy servers, and may be retrieved directly from the cache, rather than from the origin server by the caching servers, in response to similar requests from other users. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where "shared" caching servers such as "proxy" caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.

In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234.

In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234.

In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234.

In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234.

In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234.

Validate that the response does not contain sensitive, personal or user-specific information. If it does, consider the use of the following HTTP response headers, to limit, or prevent the content being stored and retrieved from the cache by another user:

Cache-Control: no-cache, no-store, must-revalidate, private

Pragma: no-cache

Expires: 0

This configuration directs both HTTP 1.0 and HTTP 1.1 compliant caching servers to not store the response, and to not retrieve the response (without validation) from the cache, in response to a similar request.