Vulnerability Scan Result

ip_address | 91.239.145.83 |
country | AL ![]() |
network_name | Ministry of Internal Affairs |
asn | AS213206 |
80/tcp | http | - - |
443/tcp | https | - - |
Software / Version | Category |
---|---|
anime.js 3.2.1 | JavaScript graphics |
jQuery Migrate 3.4.1 | JavaScript libraries |
SVG Support | WordPress plugins |
Google Font API | Font scripts |
Apache HTTP Server | Web servers |
imagesLoaded 4.1.4 | JavaScript libraries |
jQuery | JavaScript libraries |
MySQL | Databases |
Open Graph | Miscellaneous |
PHP | Programming languages |
RankMath SEO | WordPress plugins, SEO |
Twitter Emoji (Twemoji) 14.0.2 | Font scripts |
WordPress | CMS, Blogs |
wpBakery | Page builders, WordPress plugins |
WPML 4.6.9 | WordPress plugins, Translation |
RSS | Miscellaneous |
Web Application Vulnerabilities
Evidence
Risk Level | CVSS | CVE | Summary | Affected software |
---|---|---|---|---|
9.9 | CVE-2024-6386 | The WPML plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.6.12 via the Twig Server-Side Template Injection. This is due to missing input validation and sanitization on the render function. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server. | wpml 4.6.9 | |
6.4 | CVE-2025-3488 | The WPML plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpml_language_switcher shortcode in versions 3.6.0 - 4.7.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. | wpml 4.6.9 |
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. 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-1026 |
OWASP Top 10 - 2017 | |
OWASP Top 10 - 2021 |
Evidence
Software / Version | Category |
---|---|
anime.js 3.2.1 | JavaScript graphics |
jQuery Migrate 3.4.1 | JavaScript libraries |
SVG Support | WordPress plugins |
Google Font API | Font scripts |
Apache HTTP Server | Web servers |
imagesLoaded 4.1.4 | JavaScript libraries |
jQuery | JavaScript libraries |
MySQL | Databases |
Open Graph | Miscellaneous |
PHP | Programming languages |
RankMath SEO | WordPress plugins, SEO |
Twitter Emoji (Twemoji) 14.0.2 | Font scripts |
WordPress | CMS, Blogs |
wpBakery | Page builders, WordPress plugins |
WPML 4.6.9 | WordPress plugins, Translation |
RSS | 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
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
Vulnerability description
Website is accessible.
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 |
---|---|---|---|
reskosovo.rks-gov.net | A | IPv4 address | 91.239.145.83 |
reskosovo.rks-gov.net | AAAA | IPv6 address | 2a07:e0c0:4:1::3 |
reskosovo.rks-gov.net | AAAA | IPv6 address | 2a07:e0c0:3:1::3 |
reskosovo.rks-gov.net | CNAME | Canonical name | web3.rks-gov.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
Operating System | Accuracy |
---|---|
Apple iOS 4.3.1 - 4.3.5 | 98% |
Vulnerability description
OS Detection
Evidence
We managed to detect the redirect using the following Request / Response chain.
Recommendation
Vulnerability checks are skipped for ports that redirect to another port. We recommend scanning the redirected port directly.