Vulnerability Scan Result

Target:

https://fi.wikipedia.org/wiki/Johan_Ludvig_Runeberg

Scanned target: https://fi.wikipedia.org/wiki/Johan_Ludvig_Runeberg

Submitted: May 01, 2026 from UA

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

https://fi.wikipedia.org/wiki/Johan_Ludvig_Runeberg

Title:	Johan Ludvig Runeberg – Wikipedia
Description:	No description found

IP Information

ip_address	208.80.154.224
country	US
network_name	Wikimedia Foundation Inc.
asn	AS14907

Open Ports

80/tcp	http	HAProxy -
443/tcp	https	HAProxy -

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
Amazon S3	CDN
jQuery 3.7.1	JavaScript libraries
Koha	DMS
Open Graph	Miscellaneous
Perl	Programming languages
PHP	Programming languages
Redux	JavaScript frameworks
MediaWiki \1	Wikis
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://fi.wikipedia.org/wiki/Johan_Ludvig_Runeberg	WMF-Last-Access-Global	Set-Cookie: .wikipedia.org

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://fi.wikipedia.org/wiki/Johan_Ludvig_Runeberg	NetworkProbeLimit, GeoIP	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: NetworkProbeLimit=0.001 Set-Cookie: GeoIP=IT:25:Milan:45.47:9.19:v4

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
https://fi.wikipedia.org/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

Software / Version	Category
Amazon Web Services	PaaS
Amazon S3	CDN
jQuery 3.7.1	JavaScript libraries
Koha	DMS
Open Graph	Miscellaneous
Perl	Programming languages
PHP	Programming languages
Redux	JavaScript frameworks
MediaWiki \1	Wikis
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

URL	Evidence
https://fi.wikipedia.org/wiki/Johan_Ludvig_Runeberg	Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: Allow only resources downloaded over HTTPS. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). 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'. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: data: URI in default-src allows the execution of unsafe scripts. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

https://fi.wikipedia.org/wiki/Johan_Ludvig_Runeberg

Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: Allow only resources downloaded over HTTPS. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). 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'. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: data: URI in default-src allows the execution of unsafe scripts. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

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

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
MediaWiki \1	Wikis
PHP	Programming languages
Amazon Web Services	PaaS
HSTS	Security
Amazon S3	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.

Operating System	Accuracy
Apple macOS 10.13 (High Sierra) - 10.15 (Catalina) or iOS 11.0 - 13.4 (Darwin 17.0.0 - 19.2.0)	86%

Evidence

Domain Queried	DNS Record Type	Description	Value
fi.wikipedia.org	A	IPv4 address	185.15.59.224
fi.wikipedia.org	AAAA	IPv6 address	2a02:ec80:300:ed1a::1
fi.wikipedia.org	CNAME	Canonical name	dyna.wikimedia.org

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
MediaWiki \1	Wikis
PHP	Programming languages
Amazon Web Services	PaaS
Amazon S3	CDN
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.