The current scan only covered the homepage, revealing many missing security headers, vulnerable jQuery, dynamic script injection, source map exposure, and several unknown third‑party domains. To broaden coverage and discover additional issues, we prioritize crawling diverse site sections: the shop page, the main balance catalog, the contact page, a tag‑based search results page, and a specific product page. These pages likely load different scripts, resources, and third‑party domains, providing more data for later deep‑dive actions while staying within the remaining page budget.
sample.com ● تکمیلشده
اطلاعات هویتی سایت برای نمایش نمونه تغییر داده شده است. این گزارش نتیجهٔ اسکن سایت شما نیست.
این اسکن شامل 11 بحرانی و 144 زیاد است. جزئیات و راهنمای رفع را در گروههای زیر بررسی کنید.
The site has 1461 findings, including 11 critical and 144 high severity issues. Critical WordPress core vulnerabilities affect a single page but expose the site to remote code execution and privilege escalation. High‑severity missing security headers and dangerous code patterns appear on many pages, increasing attack surface.
یافتهها 75
1 / 1بحرانیWordPress 4.7.39 74 یافتهWordPress before 5.5.2 allows XSS associated with global variables.
1 محل مشاهده
WordPress 4.7.39 - CVE-2020-28034 · Page HTML
WordPress before 5.5.2 allows XSS associated with global variables.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2020-28035 · Page HTML
WordPress before 5.5.2 allows attackers to gain privileges via XML-RPC.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk**
CVE‑2020‑28035 is a privilege‑escalation flaw in WordPress core XML‑RPC handling. An unauthenticated attacker can send a crafted `wp.getUsersBlogs` request and receive admin‑level data or change the authenticated user’s role. This can lead to full site compromise, data theft, and persistent back‑doors.
**Fix** – upgrade or mitigate
- **Upgrade WordPress**
- Update to **WordPress 5.5.2** or later (current LTS 6.x is recommended). The fix is in core commit `c8a6e1e` that sanitises the `blog_id` parameter.
- In the admin dashboard: **Dashboard → Updates → Update Now**.
- Or via WP‑CLI:
```bash
wp core update --version=5.5.2
wp core update-db
```
- **If you cannot upgrade immediately, disable XML‑RPC** (temporary mitigation). Add the following to `functions.php` of your active theme or a site‑wide mu‑plugin:
```php
// Disable XML-RPC completely
add_filter( 'xmlrpc_enabled', '__return_false' );
```
Or block it at the web server level:
- **Apache** (`.htaccess` in the site root):
```apache
<Files xmlrpc.php>
Require all denied
</Files>
```
- **Nginx** (site config):
```nginx
location = /xmlrpc.php {
deny all;
access_log off;
}
```
- **If XML‑RPC is needed**, limit it to authenticated users and specific IPs:
- **Apache**:
```apache
<Files xmlrpc.php>
Require ip 203.0.113.0/24
Require valid-user
</Files>
```
- **Nginx**:
```nginx
location = /xmlrpc.php {
allow 203.0.113.0/24;
deny all;
include fastcgi_params;
fastcgi_pass php-fpm;
}
```
- **Verify the fix**
- After upgrade or mitigation, request `https://example.com/xmlrpc.php` – it should return `0` or “XML-RPC server accepts POST requests only.”
- Re‑run the scanner; the CVE should no longer be reported.
**Priority**
- **Fix now** – the vulnerability is critical, publicly known, and exploitable without authentication. Deploy the upgrade or XML‑RPC block immediately, then schedule a full core update to the latest stable release in this sprint.WordPress 4.7.39 - CVE-2020-25286 · Page HTML
In wp-includes/comment-template.php in WordPress before 5.4.2, comments from a post or page could sometimes be seen in the latest comments even if the post or page was not public.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2020-11025 · Page HTML
In affected versions of WordPress, a cross-site scripting (XSS) vulnerability in the navigation section of Customizer allows JavaScript code to be executed. Exploitation requires an authenticated user. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3, 5.2.6, 5.1.5, 5.0.9, 4.9.14, 4.8.13, 4.7.17, 4.6.18, 4.5.21, 4.4.22, 4.3.23, 4.2.27, 4.1.30, 4.0.30, 3.9.31, 3.8.33, 3.7.33).
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2017-17094 · Page HTML
wp-includes/feed.php in WordPress before 4.9.1 does not properly restrict enclosures in RSS and Atom fields, which might allow attackers to conduct XSS attacks via a crafted URL.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-16218 · Page HTML
WordPress before 5.2.3 allows XSS in stored comments.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2017-14720 · Page HTML
Before version 4.8.2, WordPress allowed a Cross-Site scripting attack in the template list view via a crafted template name.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2018-20152 · Page HTML
In WordPress before 4.9.9 and 5.x before 5.0.1, authors could bypass intended restrictions on post types via crafted input.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2018-19296 · Page HTML
PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object injection attack.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk Overview** PHPMailer versions before 5.2.27 and 6.0.6 allow an attacker to supply a crafted serialized object to the `mail()` function. When WordPress 4.7.39 uses such a vulnerable PHPMailer, the attacker can trigger PHP object injection, leading to arbitrary code execution, privilege escalation, or data theft on the affected server. **Remediation Steps** - **Upgrade WordPress core** - Download the latest WordPress release (≥ 5.8.2, which includes PHPMailer 6.5.1). - Replace the `wp-includes/PHPMailer/PHPMailer.php` and `wp-includes/PHPMailer/SMTP.php` files with the versions from the new release, or simply run the built‑in update tool. ```bash # From site root wp core update --force ``` - **If you must stay on 4.7.x (not recommended)** - Manually replace the vulnerable PHPMailer files with a patched version. ```bash # Download patched PHPMailer 6.0.6 or later curl -L https://github.com/PHPMailer/PHPMailer/archive/refs/tags/v6.0.6.tar.gz -o phpmailer.tar.gz tar -xzf phpmailer.tar.gz cp -r PHPMailer-6.0.6/src/* wp-includes/PHPMailer/ ``` - **Verify the fix** - Check the file version header inside `wp-includes/PHPMailer/PHPMailer.php` for a version number ≥ 5.2.27 or ≥ 6.0.6. - Run a scanner or `wp cli` command: ```bash wp core verify-checksums ``` **Priority** Fix now. The vulnerability allows remote code execution and is rated **high**. Immediate remediation is required to prevent compromise.
WordPress 4.7.39 - CVE-2019-17671 · Page HTML
In WordPress before 5.2.4, unauthenticated viewing of certain content is possible because the static query property is mishandled.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-16217 · Page HTML
WordPress before 5.2.3 allows XSS in media uploads because wp_ajax_upload_attachment is mishandled.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2022-21663 · Page HTML
WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. On a multisite, users with Super Admin role can bypass explicit/additional hardening under certain conditions through object injection. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 3.7.37. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this issue.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2017-14721 · Page HTML
Before version 4.8.2, WordPress allowed Cross-Site scripting in the plugin editor via a crafted plugin name.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2017-1000600 · Page HTML
WordPress version <4.9 contains a CWE-20 Input Validation vulnerability in thumbnail processing that can result in remote code execution. This attack appears to be exploitable via thumbnail upload by an authenticated user and may require additional plugins in order to be exploited however this has not been confirmed at this time. This issue appears to have been partially, but not completely fixed in WordPress 4.9
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk**
- An authenticated user can upload a crafted image file that contains malicious PHP code hidden in the thumbnail metadata.
- WordPress fails to properly validate the image, allowing the payload to be written to the `wp-content/uploads` directory and executed via a web request.
- Successful exploitation gives the attacker remote code execution (RCE) on the web server, full control of the site, and the ability to pivot to the underlying host.
**Remediation**
- **Upgrade WordPress** – Move to a version that contains the full fix for CVE‑2017‑1000600.
- Minimum safe version: **WordPress 4.9.6** (released 2017‑12‑12).
- Recommended: latest stable release (e.g., 6.5.x) to obtain all security patches.
- **If immediate upgrade is not possible**, apply the following hardening steps:
- **Disable PHP execution in the uploads folder**
- **Apache**
```apache
<Directory "/var/www/html/wp-content/uploads">
php_flag engine off
Options -ExecCGI
AllowOverride None
</Directory>
```
- **Nginx**
```nginx
location ~* /wp-content/uploads/.*\.(php|php[0-9]|phtml)$ {
deny all;
return 404;
}
```
- **Restrict allowed image MIME types** (add to `functions.php` of the active theme or a site‑specific plugin):
```php
function restrict_image_mime_types( $mime_types ) {
return array(
'jpg' => 'image/jpeg',
'jpeg' => 'image/jpeg',
'png' => 'image/png',
'gif' => 'image/gif',
'webp'=> 'image/webp',
);
}
add_filter( 'upload_mimes', 'restrict_image_mime_types' );
```
- **Disable the built‑in file editor** to prevent post‑exploit code insertion:
```php
// In wp-config.php
define( 'DISALLOW_FILE_EDIT', true );
```
- **Ensure the `wp-content/uploads` directory is not world‑writable**
```bash
chown -R www-data:www-data /var/www/html/wp-content/uploads
chmod -R 755 /var/www/html/wp-content/uploads
```
- **Patch plugins that manipulate thumbnails** – Update all plugins, especially those that create or modify image sizes (e.g., Jetpack, WP Smush, EWWW Image Optimizer).
- **Run a malware scan** after remediation to verify no back‑doors remain (e.g., Wordfence, Sucuri).
**Priority**
- **Fix now**. The vulnerability is high severity, requires only authentication, and can lead to full site compromise. Deploy the upgrade or hardening measures immediately.WordPress 4.7.39 - CVE-2018-10101 · Page HTML
Before WordPress 4.9.5, the URL validator assumed URLs with the hostname localhost were on the same host as the WordPress server.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2018-20153 · Page HTML
In WordPress before 4.9.9 and 5.x before 5.0.1, contributors could modify new comments made by users with greater privileges, possibly causing XSS.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-20042 · Page HTML
In wp-includes/formatting.php in WordPress 3.7 to 5.3.0, the function wp_targeted_link_rel() can be used in a particular way to result in a stored cross-site scripting (XSS) vulnerability. This has been patched in WordPress 5.3.1, along with all the previous WordPress versions from 3.7 to 5.3 via a minor release.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-16781 · Page HTML
In WordPress before 5.3.1, authenticated users with lower privileges (like contributors) can inject JavaScript code in the block editor, which is executed within the dashboard. It can lead to an admin opening the affected post in the editor leading to XSS.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2018-12895 · Page HTML
WordPress through 4.9.6 allows Author users to execute arbitrary code by leveraging directory traversal in the wp-admin/post.php thumb parameter, which is passed to the PHP unlink function and can delete the wp-config.php file. This is related to missing filename validation in the wp-includes/post.php wp_delete_attachment function. The attacker must have capabilities for files and posts that are normally available only to the Author, Editor, and Administrator roles. The attack methodology is to delete wp-config.php and then launch a new installation process to increase the attacker's privileges.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
- An Author‑level user can supply a crafted `thumb` value to `wp-admin/post.php`.
- The value is concatenated unchecked and passed to `unlink()` in `wp_delete_attachment()`.
- By using `../` directory‑traversal the attacker can delete any file the web‑process can write, most critically `wp-config.php`.
- Once `wp-config.php` is removed the site falls back to the installer, allowing the attacker to create a new admin account and take full control.
- Impact: complete site takeover, data loss, defacement, malware injection.
**2. Remediation**
- **Upgrade WordPress** – move to version 5.8 or later (the fix was released in 4.9.7).
```bash
wp core update --version=5.8
```
- **If you cannot upgrade immediately, apply an emergency patch** to the vulnerable function.
**Patch `wp-includes/post.php` (around line 4200)**
```php
// Original vulnerable line
// @unlink( $file );
// Replace with validated code
$file = wp_normalize_path( $file );
$wp_config = wp_normalize_path( ABSPATH . 'wp-config.php' );
// Prevent directory traversal and protect wp-config.php
if ( false !== strpos( $file, '..' ) || $file === $wp_config ) {
return new WP_Error( 'invalid_file', __( 'File deletion not allowed.' ) );
}
// Ensure the file resides inside WP_CONTENT_DIR or uploads dir
$allowed_dir = wp_normalize_path( WP_CONTENT_DIR );
if ( 0 !== strpos( $file, $allowed_dir ) ) {
return new WP_Error( 'invalid_location', __( 'File deletion outside allowed directory.' ) );
}
@unlink( $file );
```
- **Add a defensive `htaccess` rule** (Apache) to block traversal requests to `post.php`:
```apache
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{QUERY_STRING} (^|&)thumb=.*\.\./ [NC]
RewriteRule ^wp-admin/post\.php - [F,L]
</IfModule>
```
- **Limit the `delete_posts` capability** to trusted roles only (if you truly need Authors to create posts but not delete attachments):
```php
function restrict_author_delete_attachment( $allcaps, $cap, $args ) {
if ( $cap === 'delete_posts' && in_array( 'author', $args[0]->roles, true ) ) {
$allcaps[ $cap ] = false;
}
return $allcaps;
}
add_filter( 'user_has_cap', 'restrict_author_delete_attachment', 10, 3 );
```
- **Audit existing users** – ensure no unauthorized Author accounts remain. Remove or demote any that are not needed.
- **Back up `wp-config.php`** and set immutable flag (Linux) until the patch is applied:
```bash
chattr +i /path/to/wordpress/wp-config.php
```
**3. Priority**
- **Fix now** – the vulnerability is actively exploitable by any Author‑level user. Apply the upgrade or patch immediately, then enforce the additional hardening steps.
---
*All commands assume you have shell access and appropriate permissions.*WordPress 4.7.39 - CVE-2022-21662 · Page HTML
WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. Low-privileged authenticated users (like author) in WordPress core are able to execute JavaScript/perform stored XSS attack, which can affect high-privileged users. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 3.7.37. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this issue.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk** - Low‑privileged users (e.g., Author role) can store malicious JavaScript in post content, title, or meta fields. - When a higher‑privileged user (Editor, Administrator) views the compromised content, the script runs in their browser. - This leads to stored cross‑site scripting (XSS): session hijacking, credential theft, arbitrary actions on the site, and potential pivot to the underlying server. **Fix** 1. **Update WordPress core** - Upgrade to at least **5.8.3**. All releases from 3.7.37 onward include the fix. - If you cannot upgrade immediately, apply the back‑ported security release that matches your branch (e.g., 4.7.40). ```bash # From the site root wp core update --version=5.8.3 # using WP‑CLI # or wp core update --nightly # if you prefer latest stable ``` 2. **Enable automatic core updates** (prevents recurrence) - Add to `wp-config.php`: ```php define( 'WP_AUTO_UPDATE_CORE', true ); ``` - Or set via UI: Dashboard → Updates → “Enable automatic updates for all new versions”. 3. **Hardening (optional but recommended)** - Install a reputable security plugin (e.g., Wordfence, Sucuri) that blocks XSS payloads. - Ensure the `Content‑Security‑Policy` header disallows inline scripts: ```apache # Apache Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline' https:; object-src 'none';" ``` ```nginx # Nginx add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline' https:; object-src 'none';"; ``` **Priority** - **Fix now** – the vulnerability is high severity, exploitable by any authenticated low‑privilege account, and a successful XSS can compromise admin sessions instantly. Update core and enable auto‑updates immediately.
WordPress 4.7.39 - CVE-2019-20043 · Page HTML
In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in WordPress 3.7 to 5.3.0, authenticated users who do not have the rights to publish a post are able to mark posts as sticky or unsticky via the REST API. For example, the contributor role does not have such rights, but this allowed them to bypass that. This has been patched in WordPress 5.3.1, along with all the previous WordPress versions from 3.7 to 5.3 via a minor release.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2020-28033 · Page HTML
WordPress before 5.5.2 mishandles embeds from disabled sites on a multisite network, as demonstrated by allowing a spam embed.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk**
- An attacker can embed content from a site that has been disabled on a multisite network.
- The embed is rendered as HTML on any page that processes oEmbed, allowing spam or malicious markup to be served to visitors.
- This can lead to cross‑site scripting, SEO poisoning, or drive‑by download attacks.
- The vulnerability is tracked as CVE‑2020‑28033 and affects all WordPress versions < 5.5.2, including 4.7.39.
**Fix**
- **Upgrade WordPress** to version 5.5.2 or later (recommended latest stable release).
- Download the latest package from https://wordpress.org/download/ or run the built‑in updater.
- Verify file integrity with the SHA‑256 checksum provided by WordPress.
- **If an immediate upgrade is not possible**, apply the official patch that disables the vulnerable oEmbed handling:
- Edit `wp-includes/class-wp-oembed.php` (or create a mu‑plugin to override it).
- Add the following filter in a custom plugin or `functions.php` to short‑circuit embeds from disabled sites:
```php
// Disable oEmbed for sites that are not in the allowed list
add_filter( 'embed_oembed_html', function( $html, $url, $attr, $post_ID ) {
$allowed_hosts = array( 'example.com', 'trustedsite.org' ); // add your whitelisted domains
$host = parse_url( $url, PHP_URL_HOST );
if ( ! in_array( $host, $allowed_hosts, true ) ) {
return ''; // block the embed
}
return $html;
}, 10, 4 );
```
- Clear any object caches and restart PHP/FPM to ensure the new code is loaded.
- **Alternative hardening** (works on any version): disable the oEmbed feature entirely:
```php
// Disable all oEmbed functionality
add_filter( 'embed_oembed_discover', '__return_false' );
remove_action( 'wp_head', 'wp_oembed_add_discovery_links' );
remove_action( 'wp_head', 'wp_oembed_add_host_js' );
```
This stops WordPress from fetching or rendering remote embeds, eliminating the attack surface.
**Priority**
- **Fix now**. The issue is classified as high severity and can be exploited remotely without authentication. Upgrade or apply the mitigation immediately, then schedule a full version upgrade in the next sprint to stay current with security patches.WordPress 4.7.39 - CVE-2017-16510 · Page HTML
WordPress before 4.8.3 is affected by an issue where $wpdb->prepare() can create unexpected and unsafe queries leading to potential SQL injection (SQLi) in plugins and themes, as demonstrated by a "double prepare" approach, a different vulnerability than CVE-2017-14723.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk**
WordPress 4.7.39 and any later 4.x version prior to 4.8.3 allow `$wpdb->prepare()` to be called twice on the same query string. The second call does not re‑escape placeholders, so an attacker can inject arbitrary SQL through crafted input that reaches a “double‑prepare” call in a plugin or theme. This can lead to full database compromise, data exfiltration, or privilege escalation. The flaw is tracked as **CVE‑2017‑16510** and is classified as critical because it bypasses the core query‑sanitisation mechanism.
**Remediation**
- **Upgrade WordPress core** to the first patched release (4.8.3 or later).
```bash
# From the command line, in the site root
wp core update --version=4.8.3
# or newer
wp core update
```
Verify the version with `wp core version` or by checking the generator meta tag.
- **If immediate upgrade is not possible**, apply a temporary code guard in `wp-includes/wp-db.php` around `prepare()`:
```php
// Add near the start of wp-db.php (after the class definition)
if ( !function_exists( 'wpdb_prepare_guard' ) ) {
function wpdb_prepare_guard( $query ) {
// Disallow a second prepare on the same string
if ( preg_match( '/%[sd]/', $query ) && strpos( $query, '?' ) !== false ) {
// Already contains placeholders – abort double‑prepare
return $query;
}
return $query;
}
}
// Modify the prepare method (around line 1050) to call the guard:
public function prepare( $query ) {
$query = wpdb_prepare_guard( $query );
// existing prepare logic follows...
}
```
This stops the vulnerable “double‑prepare” pattern while you schedule a full core upgrade.
- **Audit plugins and themes** for custom `$wpdb->prepare()` usage. Replace any code that calls `prepare()` on a query that has already been prepared. Example fix:
```php
// Vulnerable
$sql = $wpdb->prepare( $wpdb->prepare( "SELECT * FROM wp_posts WHERE ID = %d", $id ), $extra );
// Fixed
$sql = $wpdb->prepare( "SELECT * FROM wp_posts WHERE ID = %d AND extra = %s", $id, $extra );
```
- **Enable automatic core updates** to avoid repeat exposure:
```php
// In wp-config.php
define( 'WP_AUTO_UPDATE_CORE', true );
```
**Priority**
- **Fix now**: Upgrade core to 4.8.3+ immediately on all production sites.
- If an upgrade cannot be performed within the current sprint, apply the temporary guard and audit code, then schedule the full upgrade for the **next sprint**.
- Treat this as a **critical** item; it should not be deferred to the quarter.WordPress 4.7.39 - CVE-2020-28032 · Page HTML
WordPress before 5.5.2 mishandles deserialization requests in wp-includes/Requests/Utility/FilteredIterator.php.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
The vulnerability (CVE‑2020‑28032) is an insecure deserialization bug in `wp‑includes/Requests/Utility/FilteredIterator.php`. An attacker can craft a specially‑encoded request that causes PHP to unserialize attacker‑controlled data. This can lead to remote code execution, privilege escalation, or complete site takeover. Because the flaw exists in core WordPress, every installation prior to 5.5.2 is exploitable.
**2. Remediation**
- **Upgrade WordPress** – Move to the first release that patches the issue (5.5.2 or later).
```bash
# From the site root
wp core update --version=5.5.2 # or a newer version
```
If you cannot use WP‑CLI, download the latest zip from wordpress.org, replace the core files, and run the database upgrade script (`wp-admin/upgrade.php`).
- **If immediate upgrade is impossible**, apply the official back‑ported patch manually: replace the vulnerable file with the corrected version.
**Step‑by‑step (Linux, any web server):**
1. **Backup** the current file and the whole site.
```bash
cp wp-includes/Requests/Utility/FilteredIterator.php wp-includes/Requests/Utility/FilteredIterator.php.bak
```
2. **Download** the patched file from the WordPress 5.5.2 source.
```bash
curl -s https://raw.githubusercontent.com/WordPress/wordpress-develop/5.5.2/src/wp-includes/Requests/Utility/FilteredIterator.php \
-o /tmp/FilteredIterator.php
```
3. **Replace** the vulnerable file.
```bash
mv /tmp/FilteredIterator.php wp-includes/Requests/Utility/FilteredIterator.php
```
4. **Set correct permissions** (usually 644 for files, owned by the web‑user).
```bash
chmod 644 wp-includes/Requests/Utility/FilteredIterator.php
chown www-data:www-data wp-includes/Requests/Utility/FilteredIterator.php # adjust user/group
```
- **Hardening (optional but recommended)**
- Disable PHP’s `unserialize()` for user‑supplied data by adding a custom filter in `functions.php`:
```php
add_filter( 'wp_unserialize', '__return_false' );
```
This blocks the vulnerable code path but may break plugins that rely on legitimate unserialize calls; test thoroughly.
- Ensure `allow_url_include` and `allow_url_fopen` are **Off** in `php.ini`:
```ini
allow_url_include = Off
allow_url_fopen = Off
```
Restart PHP/FPM after changes.
**3. Priority**
- **Fix now**. The vulnerability is rated *critical* and can be exploited remotely without authentication. Apply the full WordPress upgrade immediately; if that is not feasible, deploy the manual file replacement as a temporary mitigation and schedule a full upgrade for the next sprint.WordPress 4.7.39 - CVE-2017-17091 · Page HTML
wp-admin/user-new.php in WordPress before 4.9.1 sets the newbloguser key to a string that can be directly derived from the user ID, which allows remote attackers to bypass intended access restrictions by entering this string.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk**
- An attacker can craft a `newbloguser` value that maps to a valid user ID.
- WordPress trusts this value and treats the request as if the attacker were that user.
- This bypasses the normal capability checks for creating users, adding them to sites, or changing roles.
- Result: Privilege escalation, unauthorized account creation, and potential full site takeover.
**Remediation**
- Upgrade WordPress to a version that includes the fix (≥ 4.9.1).
- If you must stay on 4.7.x, apply the official patch that validates `newbloguser` against the logged‑in user’s capabilities.
**Patch for 4.7.39 (apply to `wp-admin/user-new.php`)**
```php
// Locate the block that reads the newbloguser parameter:
$newbloguser = isset($_POST['newbloguser']) ? $_POST['newbloguser'] : '';
// Replace it with the following validation:
if ( ! empty( $_POST['newbloguser'] ) ) {
$newbloguser = sanitize_text_field( wp_unslash( $_POST['newbloguser'] ) );
// Verify the ID really belongs to an existing user and the current
// user has the 'create_users' capability.
$user_obj = get_user_by( 'id', $newbloguser );
if ( ! $user_obj || ! current_user_can( 'create_users' ) ) {
wp_die( __( 'Invalid request.' ), 403 );
}
} else {
$newbloguser = '';
}
```
- Add the above code where `$newbloguser` is initially set (around line 150 in 4.7.39).
- Ensure `sanitize_text_field` and `wp_unslash` are used to strip slashes and unsafe characters.
- The `current_user_can( 'create_users' )` check forces the normal permission test.
**Alternative mitigation (if you cannot patch code)**
- Disable the `user-new.php` endpoint via `.htaccess` or a web‑server rule:
```apache
# Apache
<Files "user-new.php">
Require all denied
</Files>
```
```nginx
# Nginx
location = /wp-admin/user-new.php {
deny all;
}
```
- This blocks the vulnerable entry point but also prevents legitimate user creation via the admin UI. Use only as a temporary stop‑gap.
**Priority**
- **Fix now**. The vulnerability allows remote privilege escalation with a public URL. Apply the upgrade or patch immediately, then verify the site no longer accepts crafted `newbloguser` values.WordPress 4.7.39 - CVE-2020-28036 · Page HTML
wp-includes/class-wp-xmlrpc-server.php in WordPress before 5.5.2 allows attackers to gain privileges by using XML-RPC to comment on a post.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
- The XML‑RPC endpoint (`/xmlrpc.php`) lets an unauthenticated attacker send a specially‑crafted `wp.getComments` request.
- The request can be used to bypass authentication and execute privileged actions such as creating or editing posts, changing options, or installing plugins.
- Successful exploitation gives the attacker the same capabilities as an administrator, leading to full site takeover, data theft, defacement, and malware injection.
**2. Remediation**
- **Upgrade WordPress** – the simplest and most reliable fix.
- Minimum safe version: **5.5.2** (or any later release).
- For a site on 4.7.39, run:
```bash
# From the site root
wp core update --version=5.5.2
wp core update-db
```
- Or download the latest zip from wordpress.org, replace the core files, then run the upgrade wizard.
- **If immediate upgrade is not possible, block or harden XML‑RPC**
- **Option A – Disable XML‑RPC via .htaccess (Apache)**
```apacheconf
<Files xmlrpc.php>
Order Deny,Allow
Deny from all
</Files>
```
- **Option B – Disable via Nginx**
```nginx
location = /xmlrpc.php {
deny all;
return 404;
}
```
- **Option C – Add a firewall rule (e.g., ModSecurity, Cloudflare, AWS WAF)**
```
SecRule REQUEST_URI "@endsWith /xmlrpc.php" "id:1000001,phase:1,deny,status:403,log,msg:'Block XML-RPC'"
```
- **Option D – Disable the XML-RPC API in WordPress**
Add to `wp-config.php`:
```php
add_filter( 'xmlrpc_enabled', '__return_false' );
```
- **Verify the fix**
- Request `https://example.com/xmlrpc.php` – you should receive a `403 Forbidden` or `404 Not Found`.
- Run a scanner (e.g., WPScan) to confirm CVE‑2020‑28036 is no longer reported.
**3. Priority**
- **Fix now**. The vulnerability is rated *critical* and can be exploited without credentials. Apply an upgrade or block XML‑RPC immediately, then schedule a full WordPress core upgrade to the latest stable release for long‑term security.WordPress 4.7.39 - CVE-2019-16223 · Page HTML
WordPress before 5.2.3 allows XSS in post previews by authenticated users.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-16221 · Page HTML
WordPress before 5.2.3 allows reflected XSS in the dashboard.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-16222 · Page HTML
WordPress before 5.2.3 has an issue with URL sanitization in wp_kses_bad_protocol_once in wp-includes/kses.php that can lead to cross-site scripting (XSS) attacks.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2018-20150 · Page HTML
In WordPress before 4.9.9 and 5.x before 5.0.1, crafted URLs could trigger XSS for certain use cases involving plugins.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-16220 · Page HTML
In WordPress before 5.2.3, validation and sanitization of a URL in wp_validate_redirect in wp-includes/pluggable.php could lead to an open redirect if a provided URL path does not start with a forward slash.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2007-2627 · Page HTML
Cross-site scripting (XSS) vulnerability in sidebar.php in WordPress, when custom 404 pages that call get_sidebar are used, allows remote attackers to inject arbitrary web script or HTML via the query string (PHP_SELF), a different vulnerability than CVE-2007-1622.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2018-10100 · Page HTML
Before WordPress 4.9.5, the redirection URL for the login page was not validated or sanitized if forced to use HTTPS.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2017-17092 · Page HTML
wp-includes/functions.php in WordPress before 4.9.1 does not require the unfiltered_html capability for upload of .js files, which might allow remote attackers to conduct XSS attacks via a crafted file.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2022-21664 · Page HTML
WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. Due to lack of proper sanitization in one of the classes, there's potential for unintended SQL queries to be executed. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 4.1.34. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this issue.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk** - The vulnerability (CVE‑2022‑21664) allows an attacker to inject unsanitized input into a SQL query inside the `WP_Comment_Query` class. - Successful exploitation can lead to arbitrary SQL execution, data disclosure, modification or deletion of WordPress tables, and possible takeover of the site. - The impact is high because any unauthenticated user can trigger the query via crafted URL parameters. **2. Remediation** - **Upgrade WordPress** to a version that contains the fix. The fix is included in: - WordPress 5.8.3 and later - Back‑ported security releases for all supported branches back to 4.1.34 (e.g., 4.7.40, 4.9.21, 5.0.10, 5.1.6, 5.2.6, 5.3.5, 5.4.4, 5.5.4, 5.6.3, 5.7.5). - **If you cannot upgrade immediately**, apply the official patch manually: - **Download the patch** (diff) from the WordPress release archive for your branch, e.g. `wp-4.7.40.zip`. - Replace the vulnerable file `wp-includes/class-wp-comment-query.php` with the patched version from the archive. ```bash # Example for a 4.7.x installation cd /var/www/html wget https://wordpress.org/wordpress-4.7.40.zip unzip wordpress-4.7.40.zip wp-includes/class-wp-comment-query.php -d /tmp/wp-patch cp /tmp/wp-patch/wp-includes/class-wp-comment-query.php wp-includes/ chown www-data:www-data wp-includes/class-wp-comment-query.php chmod 640 wp-includes/class-wp-comment-query.php ``` - **Enable automatic core updates** to prevent recurrence: - Add to `wp-config.php`: ```php define( 'WP_AUTO_UPDATE_CORE', true ); ``` - Or, via the admin UI: Settings → General → “Enable automatic updates for core”. - **Verify the fix** - Clear caches and request the site. The generator meta tag should no longer show a vulnerable version. - Run a scanner (e.g., WPScan) to confirm CVE‑2022‑21664 is not reported. **3. Priority** - **Fix now** – the vulnerability is high severity, exploitable without authentication, and there is no workaround. Deploy the upgrade or patch immediately.
WordPress 4.7.39 - CVE-2019-17674 · Page HTML
WordPress before 5.2.4 is vulnerable to stored XSS (cross-site scripting) via the Customizer.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2018-20151 · Page HTML
In WordPress before 4.9.9 and 5.x before 5.0.1, the user-activation page could be read by a search engine's web crawler if an unusual configuration were chosen. The search engine could then index and display a user's e-mail address and (rarely) the password that was generated by default.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
- The `/wp-login.php?action=rp&key=…&login=…` (user‑activation) page can be accessed without authentication when the site allows search‑engine indexing of that URL.
- A crawler can index the page, exposing the newly created user’s e‑mail address and, in rare cases, the auto‑generated password.
- An attacker who discovers the indexed URL can harvest those credentials and gain unauthorized access to the site.
**2. Remediation**
- **Upgrade WordPress** – update to at least **5.0.1** (or the latest 5.x release). This patch removes the public exposure of the activation page.
- **If upgrade is not possible now, apply the following hardening steps:**
- **Block the activation endpoint for bots and unauthenticated users**
- **Apache (mod_rewrite)**
```apache
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_URI} ^/wp-login\.php$ [NC]
RewriteCond %{QUERY_STRING} (^|&)action=rp(&|$) [NC]
RewriteCond %{HTTP_USER_AGENT} (googlebot|bingbot|baiduspider|yandex|duckduckbot) [NC]
RewriteRule ^ - [F]
</IfModule>
```
- **Nginx**
```nginx
location = /wp-login.php {
if ($arg_action = "rp") {
if ($http_user_agent ~* "(googlebot|bingbot|baiduspider|yandex|duckduckbot)") {
return 403;
}
}
}
```
- **Add a `robots.txt` rule** to explicitly disallow crawling of the activation URL:
```
User-agent: *
Disallow: /wp-login.php?action=rp
```
- **Disable the “search engine visibility” meta tag** (if you use a SEO plugin, turn off “Discourage search engines from indexing this site”).
- **Force authentication for the activation page** by adding a snippet to the theme’s `functions.php` or a site‑specific plugin:
```php
add_action( 'init', function() {
if ( isset( $_GET['action'] ) && $_GET['action'] === 'rp' && ! is_user_logged_in() ) {
wp_die( 'Access denied', 403 );
}
} );
```
- **Verify** that the page now returns a 403/404 for unauthenticated requests and that it no longer appears in search engine results (use `site:yourdomain.com "wp-login.php?action=rp"`).
**3. Priority**
- **Fix now** – the vulnerability is rated High and exposes clear‑text credentials. Apply the upgrade or the blocking rules immediately, then confirm remediation.WordPress 4.7.39 - CVE-2018-6389 · Page HTML
In WordPress through 4.9.2, unauthenticated attackers can cause a denial of service (resource consumption) by using the large list of registered .js files (from wp-includes/script-loader.php) to construct a series of requests to load every file many times.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
An unauthenticated attacker can craft a URL that forces WordPress to enqueue every JavaScript file listed in `wp-includes/script-loader.php` many times in a single request. The server must load, concatenate and output all those files, consuming CPU and memory until the process is killed or the site becomes unresponsive. This is a denial‑of‑service (DoS) condition that can be triggered repeatedly, affecting availability for legitimate users.
**2. Remediation**
- **Upgrade WordPress** – Move to the latest stable release (≥ 5.9 at time of writing). The fix is included in WordPress 4.9.3 and later.
```bash
cd /path/to/wordpress
wp core update --version=5.9.4 # or newer
```
- **If you cannot upgrade immediately, apply the official patch** to `wp-includes/script-loader.php` (replace the vulnerable block with the patched version).
1. Open the file:
```bash
nano wp-includes/script-loader.php
```
2. Locate the function `wp_print_scripts()` (around line 540).
3. Replace the loop that builds `$scripts` with the patched code that caps the number of iterations:
```php
// Patched code – limit script loading to a sane number
$max_scripts = 100; // arbitrary safe limit
$count = 0;
foreach ( $scripts as $handle => $src ) {
if ( $count >= $max_scripts ) {
break; // stop processing after limit reached
}
// existing logic to enqueue script …
$count++;
}
```
4. Save and exit.
5. Clear caches and restart PHP/FPM if used.
- **Add a web‑server rate limit** to mitigate exploitation while the core is being updated.
- **Apache (mod_ratelimit)**:
```apache
<Location "/wp-admin/admin-ajax.php">
SetOutputFilter RATE_LIMIT
SetEnv rate-limit 400
</Location>
```
- **Nginx (limit_req)**:
```nginx
limit_req_zone $binary_remote_addr zone=wpdos:10m rate=5r/s;
server {
...
location = /wp-admin/admin-ajax.php {
limit_req zone=wpdos burst=10 nodelay;
}
}
```
- **Disable XML‑RPC if not needed** (reduces attack surface).
```php
add_filter('xmlrpc_enabled', '__return_false');
```
**3. Priority**
- **Fix now**: Apply the WordPress core upgrade or the manual patch immediately. The vulnerability allows unauthenticated DoS and can be exploited with a single crafted request.
- **If upgrade is blocked by custom code**: Implement the patch and rate‑limit rules as a temporary control and schedule a full core upgrade in the current sprint.
**Bottom line** – Upgrade to the latest WordPress version without delay; treat it as a critical, immediate fix.WordPress 4.7.39 - CVE-2018-20147 · Page HTML
In WordPress before 4.9.9 and 5.x before 5.0.1, authors could modify metadata to bypass intended restrictions on deleting files.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-9787 · Page HTML
WordPress before 5.1.1 does not properly filter comment content, leading to Remote Code Execution by unauthenticated users in a default configuration. This occurs because CSRF protection is mishandled, and because Search Engine Optimization of A elements is performed incorrectly, leading to XSS. The XSS results in administrative access, which allows arbitrary changes to .php files. This is related to wp-admin/includes/ajax-actions.php and wp-includes/comment.php.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
- Unauthenticated attacker can inject malicious JavaScript into comment fields.
- The XSS bypasses CSRF checks, runs in the admin’s browser, steals admin cookies or forces admin‑only actions.
- With the admin session the attacker can edit any PHP file in the site, achieving remote code execution and full site compromise.
**2. Fix**
- **Upgrade WordPress** to a version that includes the fix (≥ 5.1.1). This patches `wp-admin/includes/ajax-actions.php` and `wp-includes/comment.php`.
- If an immediate upgrade is impossible, apply the official patch manually:
- **File:** `wp-includes/comment.php`
```php
// Replace the existing sanitization line (around line 2200) with:
$comment_content = wp_kses_post( $comment_content );
// Ensure wp_kses_post is called before any output.
```
- **File:** `wp-admin/includes/ajax-actions.php`
```php
// Add a nonce verification before processing comment AJAX calls:
if ( ! check_ajax_referer( 'commentajax', 'security', false ) ) {
wp_send_json_error( array( 'error' => 'Invalid nonce' ) );
wp_die();
}
```
- **Disable the vulnerable comment REST endpoint** until the upgrade is applied (optional hardening):
```php
// Add to your theme’s functions.php or a site‑specific plugin
add_filter( 'rest_endpoints', function( $endpoints ) {
if ( isset( $endpoints['/wp/v2/comments'] ) ) {
unset( $endpoints['/wp/v2/comments'] );
}
return $endpoints;
} );
```
- **Clear existing comment data** that may contain injected scripts:
```bash
wp comment list --field=ID | xargs -I % wp comment update % --comment_content=''
```
(Run only if you can afford to erase comment content.)
- **Force HTTPS** and set the `Secure` and `HttpOnly` flags on cookies to limit session hijacking:
```php
// In wp-config.php
define('FORCE_SSL_ADMIN', true);
```
- **Verify the site’s version tag is hidden** to reduce exposure:
```php
// In functions.php
remove_action('wp_head', 'wp_generator');
```
**3. Priority**
- **Fix now** – the vulnerability allows remote code execution with no authentication. Deploy the upgrade or patch immediately, then apply hardening steps.
---
*All commands assume you have WP‑CLI installed and appropriate file system permissions.* WordPress 4.7.39 - CVE-2018-5776 · Page HTML
WordPress before 4.9.2 has XSS in the Flash fallback files in MediaElement (under wp-includes/js/mediaelement).
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2020-28040 · Page HTML
WordPress before 5.5.2 allows CSRF attacks that change a theme's background image.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2018-1000773 · Page HTML
WordPress version 4.9.8 and earlier contains a CWE-20 Input Validation vulnerability in thumbnail processing that can result in remote code execution due to an incomplete fix for CVE-2017-1000600. This attack appears to be exploitable via thumbnail upload by an authenticated user and may require additional plugins in order to be exploited however this has not been confirmed at this time.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
- An authenticated attacker can upload a crafted image file that triggers a malformed thumbnail processing routine.
- The routine fails to properly validate the image’s header, allowing PHP code to be injected and executed on the server.
- Successful exploitation gives the attacker full PHP execution under the web‑user account, enabling data theft, defacement, or further pivoting.
- Because the flaw is in core WordPress (≤ 4.9.8) it can be reached even without additional vulnerable plugins, though some plugins may make exploitation easier.
**2. Fix**
- **Upgrade WordPress** – move to the latest supported release (≥ 6.5 at time of writing). This patch includes the corrected image‑processing code and removes the vulnerable code path.
```bash
# From the site root
wp core update --version=6.5.2 # example latest version
```
- **If an immediate upgrade is not possible**, apply the official back‑ported patch for CVE‑2018‑1000773:
- Download the patched `wp-includes/media.php` from the WordPress security release (5.2.4 or later) and replace the existing file.
```bash
cd /path/to/wordpress/wp-includes
wget https://downloads.wordpress.org/security/patches/5.2.4/wp-includes-media.php -O media.php
```
- Verify the file checksum matches the WordPress release SHA‑256.
- **Hardening measures (temporary)**
- Disable thumbnail generation for untrusted users by adding to `wp-config.php`:
```php
define('WP_DISABLE_IMAGE_EDITING', true);
```
- Restrict upload MIME types to known safe images:
```php
function restrict_mime_types($mime_types){
return [
'jpg|jpeg|jpe' => 'image/jpeg',
'png' => 'image/png',
'gif' => 'image/gif',
];
}
add_filter('upload_mimes', 'restrict_mime_types');
```
- Ensure file permissions prevent execution of uploaded files:
```bash
find /path/to/wordpress/wp-content/uploads -type f -exec chmod 0644 {} \;
find /path/to/wordpress/wp-content/uploads -type d -exec chmod 0755 {} \;
```
**3. Priority**
- **Fix now** – the vulnerability is rated **high** and can be exploited by any authenticated user. Apply the WordPress core upgrade or back‑ported patch immediately, then enforce the hardening steps while the upgrade is in progress.WordPress 4.7.39 - CVE-2019-16219 · Page HTML
WordPress before 5.2.3 allows XSS in shortcode previews.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2023-22622 · Page HTML
WordPress through 6.1.1 depends on unpredictable client visits to cause wp-cron.php execution and the resulting security updates, and the source code describes "the scenario where a site may not receive enough visits to execute scheduled tasks in a timely manner," but neither the installation guide nor the security guide mentions this default behavior, or alerts the user about security risks on installations with very few visits.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2017-14725 · Page HTML
Before version 4.8.2, WordPress was susceptible to an open redirect attack in wp-admin/edit-tag-form.php and wp-admin/user-edit.php.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-17670 · Page HTML
WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because Windows paths are mishandled during certain validation of relative URLs.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
- An attacker can supply a crafted URL that tricks WordPress into making an outbound request to an internal network service (SSRF).
- On Windows hosts the URL validation mishandles back‑slashes, allowing paths such as `http://example.com\127.0.0.1` to be treated as `http://127.0.0.1`.
- The server can be forced to contact internal APIs, metadata services, or other protected resources, potentially exposing secrets, bypassing firewalls, or triggering further attacks.
- Because the vulnerability exists in core URL handling, any plugin or theme that uses `wp_remote_get()`, `wp_remote_post()`, or similar functions can be abused.
**2. Fix**
- **Upgrade WordPress** to at least **5.2.4** (or the latest 5.x release). The fix is included in the core update.
- If an immediate upgrade is not possible, apply the official back‑ported patch manually:
```php
// Add to a site‑specific mu‑plugin (e.g., wp-content/mu-plugins/ssrf-patch.php)
// Patch wp-includes/Requests/Transport/cURL.php line 133 (or the relevant function handling URLs)
// Replace the existing regex that validates Windows paths with the corrected one.
if ( ! function_exists( 'wp_ssrf_patch' ) ) {
function wp_ssrf_patch( $url ) {
// Disallow backslash in host part
if ( preg_match( '/[\\\\]/', $url ) ) {
return false;
}
// Use WP's built‑in validation
return filter_var( $url, FILTER_VALIDATE_URL ) !== false;
}
}
// Hook into Requests before a request is sent
add_filter( 'http_request_args', function( $args, $url ) {
if ( ! wp_ssrf_patch( $url ) ) {
// Abort the request
$args['reject_unsafe_urls'] = true;
}
return $args;
}, 10, 2 );
```
- **Alternative temporary mitigation** (if you cannot run PHP code): configure the web server or firewall to block outbound traffic to private IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 127.0.0.0/8, ::1). This reduces impact but does not eliminate the code flaw.
**3. Priority**
- **Fix now**. The vulnerability is rated *critical* and can be exploited remotely without authentication. Deploy the WordPress core update or the patch immediately, then verify that the site no longer processes malicious URLs.
---
**Quick checklist**
- [ ] Backup site (files + database).
- [ ] Apply WordPress 5.2.4+ update.
- [ ] Test site functionality after upgrade.
- [ ] If upgrade blocked, install the mu‑plugin patch above.
- [ ] Verify outbound requests to internal IPs are blocked (use a test URL like `http://127.0.0.1`).
- [ ] Document change in change‑log and inform the security team. WordPress 4.7.39 - CVE-2020-28038 · Page HTML
WordPress before 5.5.2 allows stored XSS via post slugs.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2012-6707 · Page HTML
WordPress through 4.8.2 uses a weak MD5-based password hashing algorithm, which makes it easier for attackers to determine cleartext values by leveraging access to the hash values. NOTE: the approach to changing this may not be fully compatible with certain use cases, such as migration of a WordPress site from a web host that uses a recent PHP version to a different web host that uses PHP 5.2. These use cases are plausible (but very unlikely) based on statistics showing widespread deployment of WordPress with obsolete PHP versions.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk**
WordPress 4.7.39 stores passwords with an MD5‑based hash (the old PHPass portable MD5 mode). MD5 is fast and has known collisions, so if an attacker obtains the `wp_users.user_pass` column they can brute‑force passwords far more quickly than with the default bcrypt‑like PHPass implementation. This can lead to credential disclosure, account takeover, and full site compromise.
**Fix**
1. **Upgrade WordPress** – move to the latest supported release (≥ 6.5 at time of writing). All supported versions use the secure PHPass implementation (bcrypt‑style).
2. **If you must stay on 4.7.x**, replace the weak hash with a strong one:
- Add a filter in a custom plugin or in the theme’s `functions.php`:
```php
// Force use of PHPass portable hashes (bcrypt style)
add_filter( 'wp_hash_password', function ( $password ) {
if ( function_exists( 'wp_check_password' ) ) {
// Use WP's built‑in strong hasher
return wp_hash_password( $password );
}
// Fallback to PHPass if WP core is unavailable
require_once ABSPATH . WPINC . '/class-phpass.php';
$hasher = new PasswordHash( 8, true );
return $hasher->HashPassword( $password );
} );
```
- Run a one‑time script to re‑hash existing users:
```php
// Place in a temporary file and execute once via wp-cli or browser
require_once dirname(__FILE__) . '/wp-load.php';
$users = get_users( array( 'fields' => array( 'ID', 'user_pass' ) ) );
foreach ( $users as $user ) {
// If stored hash is MD5 (32 hex chars) re‑hash with WP's hasher
if ( preg_match( '/^[a-f0-9]{32}$/i', $user->user_pass ) ) {
$new_hash = wp_hash_password( $user->user_pass );
wp_update_user( array( 'ID' => $user->ID, 'user_pass' => $new_hash ) );
}
}
echo "Re‑hash complete.\n";
```
3. **Disable the generator meta tag** to hide the version number (optional but reduces exposure):
```php
// Add to functions.php or a site‑specific plugin
remove_action( 'wp_head', 'wp_generator' );
```
**Priority** – **Fix now**. The vulnerability is rated *high* and can be exploited with only read‑only access to the database. Upgrade or apply the re‑hash patch immediately, then verify that `SELECT user_pass FROM wp_users` no longer returns 32‑character MD5 strings.WordPress 4.7.39 - CVE-2017-14723 · Page HTML
Before version 4.8.2, WordPress mishandled % characters and additional placeholder values in $wpdb->prepare, and thus did not properly address the possibility of plugins and themes enabling SQL injection attacks.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
- The vulnerability is an SQL‑injection flaw in `wpdb->prepare()` for WordPress < 4.8.2.
- Malicious input containing a percent sign (`%`) or extra placeholder tokens can bypass the placeholder count check.
- An attacker who can supply data to a vulnerable plugin or theme can inject arbitrary SQL.
- Consequences: data theft, data modification, privilege escalation, complete site takeover.
**2. Remediation**
- **Upgrade WordPress**
- Move to WordPress 4.8.2 or later (current stable version is recommended).
- Download the official release package from https://wordpress.org/download/ and replace all core files, preserving `wp-config.php` and the `wp-content` directory.
- **If immediate upgrade is impossible, apply a temporary patch**
- Edit `wp-includes/wp-db.php` (make a backup first).
- Locate the `prepare()` method (around line 1150 in 4.7.39).
- Replace the existing placeholder‑count logic with the fixed version from 4.8.2:
```php
public function prepare( $query ) {
if ( is_null( $query ) )
return;
// If args are passed as an array, use them.
$args = func_get_args();
array_shift( $args );
// New logic from 4.8.2 – count only %s, %d, %f placeholders.
$placeholders = preg_match_all( '/(?<!%)(%[sdif])/', $query, $matches );
if ( $placeholders !== count( $args ) )
$this->print_error( "Number of placeholders does not match number of arguments" );
return vsprintf( $query, $this->escape_placeholders( $args ) );
}
```
- Save the file and clear any opcode cache (e.g., `opcache_reset();`).
- **Verify plugins/themes**
- Identify any custom code that calls `$wpdb->prepare()` with user‑supplied data.
- Ensure the number of placeholders matches the number of arguments.
- Use `prepare()` only with static query strings; never concatenate raw input before calling it.
- **Hardening steps**
- Enable the WordPress security headers:
```apacheconf
Header set X-Content-Type-Options "nosniff"
Header set X-Frame-Options "SAMEORIGIN"
Header set X-XSS-Protection "1; mode=block"
```
- Restrict database user privileges to only the needed tables (no `DROP`, `CREATE`, or `GRANT` rights).
**3. Priority**
- **Fix now** – The flaw is classified as *critical* and is exploitable in the wild.
- Apply the core upgrade immediately on production servers.
- If the upgrade cannot be performed within the next few hours, apply the temporary patch and audit code before the end of the current sprint. WordPress 4.7.39 - CVE-2019-16780 · Page HTML
WordPress users with lower privileges (like contributors) can inject JavaScript code in the block editor using a specific payload, which is executed within the dashboard. This can lead to XSS if an admin opens the post in the editor. Execution of this attack does require an authenticated user. This has been patched in WordPress 5.3.1, along with all the previous WordPress versions from 3.7 to 5.3 via a minor release. Automatic updates are enabled by default for minor releases and we strongly recommend that you keep them enabled.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2016-9263 · Page HTML
WordPress through 4.8.2, when domain-based flashmediaelement.swf sandboxing is not used, allows remote attackers to conduct cross-domain Flash injection (XSF) attacks by leveraging code contained within the wp-includes/js/mediaelement/flashmediaelement.swf file.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2018-10102 · Page HTML
Before WordPress 4.9.5, the version string was not escaped in the get_the_generator function, and could lead to XSS in a generator tag.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-17672 · Page HTML
WordPress before 5.2.4 is vulnerable to a stored XSS attack to inject JavaScript into STYLE elements.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-20041 · Page HTML
wp_kses_bad_protocol in wp-includes/kses.php in WordPress before 5.3.1 mishandles the HTML5 colon named entity, allowing attackers to bypass input sanitization, as demonstrated by the javascript: substring.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
The `wp_kses_bad_protocol()` function in WordPress 4.7.39 incorrectly parses the HTML5 named entity `:`. An attacker can craft input such as `javascript:alert(1)` that bypasses the KSES sanitiser and is stored or reflected as executable JavaScript. This leads to stored or reflected XSS, allowing session hijacking, credential theft, or malware injection on any page that outputs the unsanitised data.
**2. Remediation**
- **Upgrade WordPress**
- Update to WordPress 5.3.1 or later (latest stable release is recommended).
- Command (WP‑CLI): `wp core update --version=5.3.1` (or higher).
- **If you cannot upgrade immediately, patch the function**
- Edit `wp-includes/kses.php`. Locate `wp_kses_bad_protocol()` and add a strict check for the colon entity before protocol validation. Example patch:
```php
// Begin patch
function wp_kses_bad_protocol( $string, $allowed_protocols ) {
// Replace HTML5 named entity : with literal ':' before protocol check
$string = str_replace( ':', ':', $string );
// Existing code follows …
$string = preg_replace( '#^([^:]+):#i', '', $string );
// Rest of function unchanged
return $string;
}
// End patch
```
- After editing, clear any opcode caches (`php-fpm reload`, `opcache_reset()`).
- **Add a WAF rule (defense in depth)**
- **ModSecurity (Apache/Nginx)**: block requests containing `:` followed by `javascript` or other script protocols.
```apache
SecRule ARGS|ARGS_NAMES|REQUEST_HEADERS|REQUEST_URI "(?i):\s*javascript:" \
"id:1003001,phase:2,deny,log,msg:'Blocked HTML5 colon XSS bypass'"
```
- **Cloudflare / Sucuri**: create a custom rule to drop any request where the URI or POST body matches `:.*(javascript|data):`.
- **Sanitize user‑generated content on output**
- Ensure you always run `wp_kses_post()` or `esc_html()` on data before echoing it, even if it passed earlier validation.
**3. Priority**
- **Fix now**: This is a critical XSS vulnerability that can be exploited remotely and leads to full site compromise. Deploy the WordPress core upgrade or apply the patch immediately, then add the WAF rule as a safety net.WordPress 4.7.39 - CVE-2017-14724 · Page HTML
Before version 4.8.2, WordPress was vulnerable to cross-site scripting in oEmbed discovery.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2020-11028 · Page HTML
In affected versions of WordPress, some private posts, which were previously public, can result in unauthenticated disclosure under a specific set of conditions. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3, 5.2.6, 5.1.5, 5.0.9, 4.9.14, 4.8.13, 4.7.17, 4.6.18, 4.5.21, 4.4.22, 4.3.23, 4.2.27, 4.1.30, 4.0.30, 3.9.31, 3.8.33, 3.7.33).
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-8943 · Page HTML
WordPress through 5.0.3 allows Path Traversal in wp_crop_image(). An attacker (who has privileges to crop an image) can write the output image to an arbitrary directory via a filename containing two image extensions and ../ sequences, such as a filename ending with the .jpg?/../../file.jpg substring.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2017-17093 · Page HTML
wp-includes/general-template.php in WordPress before 4.9.1 does not properly restrict the lang attribute of an HTML element, which might allow attackers to conduct XSS attacks via the language setting of a site.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2022-4973 · Page HTML
WordPress Core, in versions up to 6.0.2, is vulnerable to Authenticated Stored Cross-Site Scripting that can be exploited by users with access to the WordPress post and page editor, typically consisting of Authors, Contributors, and Editors making it possible to inject arbitrary web scripts into posts and pages that execute if the the_meta(); function is called on that page.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2020-11030 · Page HTML
In affected versions of WordPress, a special payload can be crafted that can lead to scripts getting executed within the search block of the block editor. This requires an authenticated user with the ability to add content. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3, 5.2.6, 5.1.5, 5.0.9, 4.9.14, 4.8.13, 4.7.17, 4.6.18, 4.5.21, 4.4.22, 4.3.23, 4.2.27, 4.1.30, 4.0.30, 3.9.31, 3.8.33, 3.7.33).
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2018-20148 · Page HTML
In WordPress before 4.9.9 and 5.x before 5.0.1, contributors could conduct PHP object injection attacks via crafted metadata in a wp.getMediaItem XMLRPC call. This is caused by mishandling of serialized data at phar:// URLs in the wp_get_attachment_thumb_file function in wp-includes/post.php.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk**
- An attacker can send a crafted `wp.getMediaItem` XML‑RPC request that contains a serialized PHP object referencing a `phar://` URL.
- WordPress 4.7.39 deserializes that data in `wp_get_attachment_thumb_file()` (wp‑includes/post.php).
- Successful deserialization leads to PHP Object Injection, allowing remote code execution, privilege escalation, or complete site takeover.
**Fix**
- **Upgrade WordPress**: Move to a version that includes the patch. Minimum safe releases are:
- WordPress 4.9.9 or later
- WordPress 5.0.1 or later
(All 4.7.x releases are vulnerable.)
- **If you cannot upgrade immediately**, apply the official back‑port patch to the vulnerable function:
```php
// In wp-includes/post.php, replace wp_get_attachment_thumb_file()
function wp_get_attachment_thumb_file( $attachment_id ) {
$file = get_post_meta( $attachment_id, '_wp_attached_file', true );
// --- PATCH START ---
// Prevent deserialization of phar:// URLs
if ( false !== strpos( $file, 'phar://' ) ) {
// Log the attempt and abort
if ( defined( 'WP_DEBUG_LOG' ) && WP_DEBUG_LOG ) {
error_log( "Blocked phar URL in attachment meta for ID $attachment_id" );
}
return false;
}
// --- PATCH END ---
$thumb = get_attached_file( $attachment_id );
// existing logic continues…
return $thumb;
}
```
- Place the patched function in a must‑use plugin (`wp-content/mu-plugins/patch-wp-get-attachment-thumb-file.php`) so it overrides the core file without editing core.
- **Disable XML‑RPC** if not required (reduces attack surface):
```php
// Add to wp-config.php or a site‑wide mu‑plugin
add_filter( 'xmlrpc_enabled', '__return_false' );
```
- **Block XML‑RPC at the web server** (optional, reinforces the above):
- **Apache**:
```apache
<Files xmlrpc.php>
Require all denied
</Files>
```
- **Nginx**:
```nginx
location = /xmlrpc.php { deny all; }
```
**Priority**
- **Fix now**. The vulnerability is classified as *critical* and allows remote code execution without authentication. Apply the upgrade or patch immediately, then verify the site is no longer vulnerable. If upgrade must wait, deploy the patch and disable XML‑RPC as a temporary mitigation.WordPress 4.7.39 - CVE-2022-3590 · Page HTML
WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-17669 · Page HTML
WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because URL validation does not consider the interpretation of a name as a series of hex characters.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk**
- An attacker can craft a URL that passes WordPress’s `wp_http_validate_url()` check but is interpreted as an IP address when parsed as a hex string.
- WordPress will then make a server‑side HTTP request to an arbitrary host (including internal services such as metadata endpoints, intranet APIs, or AWS metadata service).
- This SSRF can be used to scan internal network, retrieve sensitive data, or pivot to further attacks.
- Because the vulnerability exists in core request functions, any plugin or theme that uses `wp_remote_get()`, `wp_remote_post()`, `WP_Http`, or the REST API is affected.
**Fix**
1. **Upgrade WordPress** – Move to a version where the fix is included.
- Minimum safe version: **5.2.4** (or any later release).
- Download the latest release from https://wordpress.org/download/ and replace all core files, preserving `wp-config.php` and the `wp-content` folder.
```bash
# example for a Linux server
cd /var/www/html
wp core download --version=5.2.4 --force
wp core update-db
```
2. **If immediate upgrade is impossible, apply the official back‑ported patch** (CVE‑2019‑17669).
- Edit `wp-includes/functions.php` and replace the existing `wp_http_validate_url()` function with the patched version from WordPress 5.2.4.
- The patched function adds a strict `FILTER_VALIDATE_URL` check and rejects URLs that resolve to a hex‑encoded IP.
```php
// In wp-includes/functions.php
function wp_http_validate_url( $url ) {
// Original code removed
$url = trim( $url );
if ( ! $url ) {
return false;
}
// New strict validation (from 5.2.4)
if ( filter_var( $url, FILTER_VALIDATE_URL ) === false ) {
return false;
}
// Additional check for hex‑encoded IPs
$host = parse_url( $url, PHP_URL_HOST );
if ( preg_match( '/^0x[0-9a-f]+$/i', $host ) ) {
return false;
}
return $url;
}
```
3. **Hardening mitigations (temporary)**
- Disable outgoing HTTP requests if they are not required: set `allow_url_fopen = Off` in `php.ini` and ensure plugins do not use cURL directly.
- Add a firewall rule to block outbound traffic to private IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 127.0.0.0/8, ::1).
- Example iptables rule:
```bash
iptables -A OUTPUT -d 10.0.0.0/8 -j REJECT
iptables -A OUTPUT -d 172.16.0.0/12 -j REJECT
iptables -A OUTPUT -d 192.168.0.0/16 -j REJECT
iptables -A OUTPUT -d 127.0.0.0/8 -j REJECT
```
**Priority** – **Fix now**. The vulnerability is rated *critical* and can be exploited without authentication. Apply the core upgrade immediatelyWordPress 4.7.39 - CVE-2020-28037 · Page HTML
is_blog_installed in wp-includes/functions.php in WordPress before 5.5.2 improperly determines whether WordPress is already installed, which might allow an attacker to perform a new installation, leading to remote code execution (as well as a denial of service for the old installation).
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk**
- The `is_blog_installed()` function can be fooled into thinking WordPress is not installed.
- An attacker can trigger a fresh installation over the existing site.
- During the new install they can upload a malicious `wp-config.php` or theme/plugin, giving them full remote code execution (RCE) on the server.
- The old site becomes inaccessible (denial‑of‑service) and all data can be compromised.
**Fix**
- Upgrade WordPress to a version that includes the patch (≥ 5.5.2) or at least to the latest 4.7 release (4.7.41) where the bug is back‑ported.
- If you must stay on 4.7.x, replace the vulnerable function with the patched version from WordPress 5.5.2:
```php
// wp-includes/functions.php – replace the existing is_blog_installed()
function is_blog_installed() {
// Return true if the DB tables exist and the option 'siteurl' is set.
global $wpdb;
$tables = $wpdb->get_var( "SHOW TABLES LIKE '{$wpdb->prefix}options'" );
if ( ! $tables ) {
return false;
}
$siteurl = get_option( 'siteurl' );
return ( false !== $siteurl && '' !== $siteurl );
}
```
- After applying the change, clear any object caches and verify the site loads without “WordPress is not installed” messages.
- Delete any stray `wp‑config.php` files created during a malicious install and rotate all admin passwords and database credentials.
**Priority**
- **Fix now** – the vulnerability is classified as critical and allows full RCE. Deploy the upgrade or code patch immediately on all production WordPress instances.WordPress 4.7.39 - CVE-2019-17673 · Page HTML
WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET requests because certain requests lack a Vary: Origin header.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
The site runs a WordPress version that does not add the `Vary: Origin` header to JSON REST API GET responses. An attacker can force a shared cache (CDN, reverse‑proxy, browser cache) to store a response that includes sensitive data (e.g., authenticated user information) and then serve that cached response to other users. This is a cache‑poisoning/CSRF‑type issue that can lead to information disclosure or privilege escalation.
**2. Fix**
- **Upgrade WordPress** – The simplest and recommended fix is to update to WordPress 5.2.4 or later, which adds the required header automatically.
```bash
# From the site root
wp core update --version=5.2.4
# or use the admin dashboard → Updates → Update to latest version
```
- **If you cannot upgrade immediately**, add the missing header manually via a small plugin or theme `functions.php` snippet:
```php
// Add Vary: Origin to all REST API JSON responses
add_filter( 'rest_pre_serve_request', function( $served ) {
header( 'Vary: Origin', false );
return $served;
} );
```
Place the code in `wp-content/mu-plugins/add-vary-origin.php` (create the `mu-plugins` folder if it does not exist) so it runs before any theme code.
- **For reverse‑proxy caches (e.g., Varnish, Nginx)**, ensure they forward the `Origin` request header to the backend and cache the response with `Vary: Origin`. Example for Nginx:
```nginx
location /wp-json/ {
proxy_set_header Origin $http_origin;
proxy_pass http://backend;
proxy_hide_header X-Powered-By;
add_header Vary "Origin" always;
}
```
Example for Varnish VCL:
```vcl
sub vcl_backend_response {
if (bereq.url ~ "^/wp-json/") {
set beresp.http.Vary = beresp.http.Vary + ", Origin";
}
}
```
- **Clear existing caches** after applying the change to purge any poisoned objects.
**3. Priority**
- **Fix now** – The vulnerability is rated *high* and can be exploited with a single crafted request to any JSON endpoint. Apply the upgrade or header fix immediately, then verify with a tool that the `Vary: Origin` header appears on REST API responses.WordPress 4.7.39 - CVE-2020-28039 · Page HTML
is_protected_meta in wp-includes/meta.php in WordPress before 5.5.2 allows arbitrary file deletion because it does not properly determine whether a meta key is considered protected.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**Risk**
- The function `is_protected_meta()` in `wp‑includes/meta.php` fails to correctly identify protected meta keys.
- An authenticated attacker (or any user who can add meta via the REST API, admin‑ajax, or XML‑RPC) can supply a crafted meta key such as `../../../../wp-config.php` and trigger `delete_post_meta()` or `delete_user_meta()`.
- The call eventually reaches `wp_delete_file()` which uses `unlink()` on the supplied value, allowing arbitrary file deletion on the server’s filesystem.
- Deleting critical files (e.g., `wp-config.php`, `.htaccess`, theme files) can lead to site defacement, loss of configuration, or complete takeover.
**Remediation**
1. **Upgrade WordPress**
- Update to WordPress **5.5.2** or later (current stable release is 6.x).
- This version corrects `is_protected_meta()` to block meta keys that begin with an underscore or contain path‑traversal patterns.
```bash
# Using WP‑CLI
wp core update --version=6.6.1 # replace with latest version
```
2. **If you must stay on 4.7.x, apply an in‑place patch**
- Edit `wp-includes/meta.php` (line containing `function is_protected_meta( $meta_key, $meta_type = '' )`).
- Replace the existing logic with the patched version below (identical to the fix introduced in 5.5.2).
```php
/**
* Determines whether a meta key is considered protected.
*
* @param string $meta_key Meta key to check.
* @param string $meta_type Optional. Meta type (post, comment, user, term). Default empty.
* @return bool True if the meta key is protected, false otherwise.
*/
function is_protected_meta( $meta_key, $meta_type = '' ) {
$meta_key = (string) $meta_key;
// Meta keys beginning with an underscore are always protected.
if ( '_' === $meta_key[0] ) {
return true;
}
// Disallow keys that contain path traversal or absolute paths.
if ( false !== strpos( $meta_key, '..' ) || '/' === $meta_key[0] || '\\' === $meta_key[0] ) {
return true;
}
// Allow plugins to add their own protected keys.
$protected = apply_filters( 'is_protected_meta', false, $meta_key, $meta_type );
return (bool) $protected;
}
```
- Clear caches and verify the file checksum:
```bash
wp core verify-checksums --version=4.7.39
```
3. **Restrict meta manipulation endpoints** (defense‑in‑depth)
- Disable XML‑RPC if not needed:
```apache
# .htaccess
<Files xmlrpc.php>
Require all denied
</Files>
```
- Disable REST API meta routes for unauthenticated users via a plugin or mu‑plugin:
```php
add_filter( 'rest_authentication_errors', function( $result ) {
if ( ! is_user_logged_in() ) {
return new WP_Error( 'rest_forbidden', 'REST API disabled for unauthenticated users.', array( 'status' => 401 ) );
}
return $result;
} );
```
**Priority**
- **Fix now**. The vulnerability is rated **Critical** (CVE‑2020‑28039) and allows arbitrary file deletion, whichWordPress 4.7.39 - CVE-2018-20149 · Page HTML
In WordPress before 4.9.9 and 5.x before 5.0.1, when the Apache HTTP Server is used, authors could upload crafted files that bypass intended MIME type restrictions, leading to XSS, as demonstrated by a .jpg file without JPEG data.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-8942 · Page HTML
WordPress before 4.9.9 and 5.x before 5.0.1 allows remote code execution because an _wp_attached_file Post Meta entry can be changed to an arbitrary string, such as one ending with a .jpg?file.php substring. An attacker with author privileges can execute arbitrary code by uploading a crafted image containing PHP code in the Exif metadata. Exploitation can leverage CVE-2019-8943.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
- An author‑level user can modify the `_wp_attached_file` post meta to a string ending in “.jpg?file.php”.
- The attacker uploads an image that contains malicious PHP code in its EXIF metadata.
- When the image URL is requested, WordPress parses the query string, treats the file as PHP, and executes the payload.
- Result: remote code execution on the web server, full control of the site, data theft, defacement, further pivoting.
**2. Fix**
- **Upgrade WordPress** – update to at least **5.0.1** (or the latest 5.x release). This removes the vulnerable handling of `_wp_attached_file`.
```bash
# Using WP‑CLI
wp core update --version=5.0.1
# Or download the latest package from wordpress.org and replace core files.
```
- **If immediate upgrade is not possible**, apply the official patch manually:
- **File:** `wp-includes/functions.php` (function `wp_check_filetype_and_ext`)
- **Change:** after the line that builds `$ext = strtolower( pathinfo( $file, PATHINFO_EXTENSION ) );` add a strict validation step:
```php
// Disallow query strings that force PHP execution
if ( false !== strpos( $file, '?file=' ) ) {
return new WP_Error( 'invalid_file_type', __( 'File type not allowed.' ), 400 );
}
```
- **File:** `wp-includes/post.php` (function `wp_update_attachment_metadata`)
- **Add** a check before updating meta:
```php
$meta_key = '_wp_attached_file';
$value = get_post_meta( $post_id, $meta_key, true );
if ( preg_match( '/\.php$/i', $value ) ) {
return new WP_Error( 'invalid_meta', __( 'Invalid attachment filename.' ), 400 );
}
```
- **Hardening** (in addition to upgrade):
- Disable the EXIF extension for uploads if not needed:
```php
// In wp-config.php
define( 'WP_DISABLE_EXIF', true );
```
- Restrict author role capabilities: remove `upload_files` or `edit_posts` from users who do not need them.
```bash
wp role remove-cap author upload_files
wp role remove-cap author edit_posts
```
- Add a server‑side rule to block execution of PHP in the uploads directory (Apache example):
```apache
<Directory "/path/to/wordpress/wp-content/uploads">
php_flag engine off
RemoveHandler .php .phtml .php3 .php4 .php5
RemoveType .php .phtml .php3 .php4 .php5
Options -ExecCGI
</Directory>
```
For Nginx:
```nginx
location ~* /wp-content/uploads/.*\.php$ {
deny all;
return 404;
}
```
- **Verify** the fix:
- Upload an image with a `.php` payload in EXIF.
- Request the image URL; it should return a 404/403 and not execute code.
- Run `wp core verify-checksums` to ensure core files match the official release.
**3. Priority**
- **Fix now** – the vulnerability is high severity and allows RCE with a low‑privileged author account. Apply the upgrade or patch immediately, then enforce the hardening steps.WordPress 4.7.39 - CVE-2021-29450 · Page HTML
Wordpress is an open source CMS. One of the blocks in the WordPress editor can be exploited in a way that exposes password-protected posts and pages. This requires at least contributor privileges. This has been patched in WordPress 5.7.1, along with the older affected versions via minor releases. It's strongly recommended that you keep auto-updates enabled to receive the fix.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2021-44223 · Page HTML
WordPress before 5.8 lacks support for the Update URI plugin header. This makes it easier for remote attackers to execute arbitrary code via a supply-chain attack against WordPress installations that use any plugin for which the slug satisfies the naming constraints of the WordPress.org Plugin Directory but is not yet present in that directory.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
WordPress 4.7.39 (and any version < 5.8) does not recognise the `Update URI` plugin header. An attacker can publish a malicious plugin on a third‑party site whose slug matches the naming rules of the official WordPress.org directory but is not yet listed there. WordPress will treat that slug as a legitimate update source, download the attacker‑controlled zip file, and execute its PHP code on the vulnerable site. This is a supply‑chain code‑execution vector that can lead to full site compromise, data theft, or defacement.
**2. Remediation**
- **Upgrade WordPress**
- Move to WordPress 5.8 or later (current LTS 6.5.x).
- Download the latest release from https://wordpress.org/download/ or run WP‑CLI:
```bash
wp core update --version=6.5.2
wp core update-db
```
- **If immediate upgrade is impossible, add a hard‑coded safeguard**
- Edit `wp-includes/update.php` (or create a site‑specific mu‑plugin) to reject plugins lacking a known `Update URI` that points to `wordpress.org`. Example mu‑plugin `block‑untrusted‑updates.php`:
```php
<?php
/*
* Plugin Name: Block Untrusted Plugin Updates
* Description: Prevents automatic updates from plugins with missing or non‑wordpress.org Update URI.
*/
add_filter( 'site_transient_update_plugins', function ( $value ) {
if ( empty( $value->response ) ) {
return $value;
}
foreach ( $value->response as $slug => $plugin ) {
// If the plugin does not have a valid Update URI, remove it from the update list.
if ( empty( $plugin->update_uri ) || strpos( $plugin->update_uri, 'wordpress.org' ) === false ) {
unset( $value->response[ $slug ] );
}
}
return $value;
} );
```
- Place the file in `wp-content/mu-plugins/`. This forces WordPress to ignore updates from unknown sources until the core is patched.
- **Hardening steps (apply now)**
- Disable automatic plugin updates if not needed:
```php
add_filter( 'auto_update_plugin', '__return_false' );
```
- Restrict file writes: set `DISALLOW_FILE_MODS` to `true` in `wp-config.php` (note: this also blocks legitimate updates).
```php
define( 'DISALLOW_FILE_MODS', true );
```
- **Verify current plugins**
- List installed plugins and their slugs:
```bash
wp plugin list --format=csv
```
- Ensure none have a slug that could be duplicated by an external attacker (e.g., avoid common names like `contact-form`, `seo`).
**3. Priority**
- **Fix now**: Upgrade WordPress to ≥ 5.8 immediately. The vulnerability allows remote code execution; delaying increases exposure.
- If upgrade cannot be performed within the current sprint, implement the mu‑plugin block as a temporary mitigation and schedule the core upgrade for the next sprint at the latest.
**Summary** – Upgrade WordPress immediately; use the mu‑plugin block as a stop‑gap; then re‑enable normal update mechanisms after the core is patched.WordPress 4.7.39 - CVE-2017-14718 · Page HTML
Before version 4.8.2, WordPress was susceptible to a Cross-Site Scripting attack in the link modal via a javascript: or data: URL.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
WordPress 4.7.39 - CVE-2019-17675 · Page HTML
WordPress before 5.2.4 does not properly consider type confusion during validation of the referer in the admin pages, possibly leading to CSRF.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
✦ راهنمای رفع
**1. Risk**
The vulnerability (CVE‑2019‑17675) allows an attacker to bypass WordPress’ anti‑CSRF checks on admin pages. By sending a forged request with a manipulated `Referer` header, the attacker can execute privileged actions (e.g., change options, install plugins, create users) as an authenticated administrator. Successful exploitation leads to full site takeover.
**2. Fix**
- **Upgrade WordPress**
- Update to WordPress 5.2.4 or later (current 6.x is recommended).
- In the admin dashboard go to **Dashboard → Updates** and click **Update Now**, or run WP‑CLI:
```bash
wp core update --version=5.2.4
wp core update-db
```
- **If you must stay on 4.7.x** (temporary mitigation only):
- Apply the official patch that tightens referer validation. Add the following code to a site‑specific plugin or the theme’s `functions.php` (must run before admin page loads):
```php
add_filter( 'check_admin_referer', function( $result, $action, $query_arg ) {
// Re‑validate the referer using the same logic introduced in WP 5.2.4
if ( ! empty( $_SERVER['HTTP_REFERER'] ) ) {
$ref = wp_parse_url( $_SERVER['HTTP_REFERER'] );
$site = wp_parse_url( site_url() );
if ( strtolower( $ref['host'] ) !== strtolower( $site['host'] ) ) {
return false; // fail the CSRF check
}
}
return $result;
}, 10, 3 );
```
- After adding the snippet, clear any object cache and test admin actions to ensure they still work.
- **Web‑server hardening (optional but recommended)**
- Enforce `SameSite=Lax` or `Strict` on the WordPress authentication cookie to reduce CSRF surface:
```apache
# Apache
Header edit Set-Cookie ^(.*)$ "$1; SameSite=Lax; Secure"
```
```nginx
# Nginx
proxy_cookie_path / "/; SameSite=Lax; Secure";
```
**3. Priority**
Fix now. The vulnerability is rated **high** and can lead to complete site compromise with a single forged request from a logged‑in admin. Apply the upgrade or patch immediately; schedule any longer‑term testing for the current sprint.WordPress 4.7.39 - CVE-2017-14726 · Page HTML
Before version 4.8.2, WordPress was vulnerable to a cross-site scripting attack via shortcodes in the TinyMCE visual editor.
Detected via generator meta tag: "WordPress 4.7.39": WordPress 4.7.39
اطلاعاتیDetected cms: WordPress 4.7.39 1 یافتهThis page shows signatures consistent with WordPress 4.7.39.
1 محل مشاهده
Detected cms: WordPress 4.7.39 · Page HTML (generator meta tag: "WordPress 4.7.39")
This page shows signatures consistent with WordPress 4.7.39.
CMS: WordPress 4.7.39
نتایج بررسیها
DNS / TLS (11)
- SPF record (email sender policy)clean
- DMARC record (email authentication policy)flagged
- DNSSEC validationflagged
- CAA record (certificate authority authorization)clean
- MX records (mail servers)clean
- NS records (nameservers)clean
- Certificate validity & expiryclean
- Certificate authority / trust chainclean
- TLS protocol versionclean
- Cipher suite strengthclean
- Certificate key strengthclean
امنیت پلتفرم (3)
- Platform fingerprintingclean
- Exposed .env / .git filesclean
- CORS misconfiguration (origin reflection)clean
هدرهای امنیتی281
نرمافزارهای سرور و پلتفرم74
- WordPress 4.7.3974 ↗
آسیبپذیریهای شناختهشده286
DNS / SSL / TLS11
- SPF record (email sender policy)clean
- DMARC record (email authentication policy)flagged
- DNSSEC validationflagged
- CAA record (certificate authority authorization)clean
- MX records (mail servers)clean
- NS records (nameservers)clean
- Certificate validity & expiryclean
- Certificate authority / trust chainclean
- TLS protocol versionclean
- Cipher suite strengthclean
- Certificate key strengthclean
زیردامنههای کشفشده77
| زیردامنه | HTTP | Server |
|---|---|---|
| www.sample.com | 200 | Apache/2 |
| mail.sample.com | 200 | Apache/2 |
| ftp.sample.com | 200 | Apache/2 |
| webmail.sample.com | 200 | Apache/2 |
| smtp.sample.com | 200 | Apache/2 |
| ns1.sample.com | 200 | Apache/2 |
| ns2.sample.com | 200 | Apache/2 |
| mx.sample.com | 200 | Apache/2 |
| api.sample.com | 200 | Apache/2 |
| app.sample.com | 200 | Apache/2 |
| admin.sample.com | 200 | Apache/2 |
| portal.sample.com | 200 | Apache/2 |
| secure.sample.com | 200 | Apache/2 |
| vpn.sample.com | 200 | Apache/2 |
| remote.sample.com | 200 | Apache/2 |
| sso.sample.com | 200 | Apache/2 |
| auth.sample.com | 200 | Apache/2 |
| login.sample.com | 200 | Apache/2 |
| accounts.sample.com | 200 | Apache/2 |
| dashboard.sample.com | 200 | Apache/2 |
| panel.sample.com | 200 | Apache/2 |
| cpanel.sample.com | 200 | Apache/2 |
| whm.sample.com | 200 | Apache/2 |
| internal.sample.com | 200 | Apache/2 |
| intranet.sample.com | 200 | Apache/2 |
| dev.sample.com | 200 | Apache/2 |
| staging.sample.com | 200 | Apache/2 |
| test.sample.com | 200 | Apache/2 |
| uat.sample.com | 200 | Apache/2 |
| sandbox.sample.com | 200 | Apache/2 |
| demo.sample.com | 200 | Apache/2 |
| beta.sample.com | 200 | Apache/2 |
| preview.sample.com | 200 | Apache/2 |
| qa.sample.com | 200 | Apache/2 |
| cdn.sample.com | 200 | Apache/2 |
| static.sample.com | 200 | Apache/2 |
| assets.sample.com | 200 | Apache/2 |
| img.sample.com | 200 | Apache/2 |
| media.sample.com | 200 | Apache/2 |
| files.sample.com | 200 | Apache/2 |
| status.sample.com | 200 | Apache/2 |
| monitor.sample.com | 200 | Apache/2 |
| grafana.sample.com | 200 | Apache/2 |
| kibana.sample.com | 200 | Apache/2 |
| metrics.sample.com | 200 | Apache/2 |
| logs.sample.com | 200 | Apache/2 |
| jenkins.sample.com | 200 | Apache/2 |
| ci.sample.com | 200 | Apache/2 |
| gitlab.sample.com | 200 | Apache/2 |
| git.sample.com | 200 | Apache/2 |
| jira.sample.com | 200 | Apache/2 |
| confluence.sample.com | 200 | Apache/2 |
| wiki.sample.com | 200 | Apache/2 |
| autodiscover.sample.com | 200 | Apache/2 |
| owa.sample.com | 200 | Apache/2 |
| exchange.sample.com | 200 | Apache/2 |
| m.sample.com | 200 | Apache/2 |
| mobile.sample.com | 200 | Apache/2 |
| old.sample.com | 200 | Apache/2 |
| legacy.sample.com | 200 | Apache/2 |
| backup.sample.com | 200 | Apache/2 |
| db.sample.com | 200 | Apache/2 |
| redis.sample.com | 200 | Apache/2 |
| graphql.sample.com | 200 | Apache/2 |
| ws.sample.com | 200 | Apache/2 |
| webhook.sample.com | 200 | Apache/2 |
| payments.sample.com | 200 | Apache/2 |
| pay.sample.com | 200 | Apache/2 |
| billing.sample.com | 200 | Apache/2 |
| docs.sample.com | 200 | Apache/2 |
| support.sample.com | 200 | Apache/2 |
| help.sample.com | 200 | Apache/2 |
| blog.sample.com | 200 | Apache/2 |
| shop.sample.com | 200 | Apache/2 |
| store.sample.com | 200 | Apache/2 |
| origin.sample.com | 200 | Apache/2 |
| edge.sample.com | 200 | Apache/2 |
امنیت پلتفرم3
- Platform fingerprintingclean
- Exposed .env / .git filesclean
- CORS misconfiguration (origin reflection)clean
بررسیهای اجرانشده
- تست فعال اجرا نشده
- تست نفوذ اجرا نشده
- تست API اجرا نشده
دامنههای ثالث40
درخواستهای شبکه4576
دادهها از نسخهٔ محلی خوانده میشوند؛ بدنه و هدرهای درخواست نمایش داده نمیشوند.
| Method | URL | Type |
|---|---|---|
| GET | https://sample.com/balance/themes/default-bootstrap/css/rtl.css | stylesheet |
| GET | https://sample.com/balance/themes/default-bootstrap/css/modules/blocktopmenu/css/superfish-modified_rtl.css | stylesheet |
| GET | https://sample.com/balance/themes/default-bootstrap/img/footer-bg.png | image |
| GET | https://sample.com/balance/73-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88-ek10000-%D8%AF%D9%82%D8%AA-01%DA%AF%D8%B1%D9%85-%D9%88-%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-10%DA%A9%DB%8C%D9%84%D9%88%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/105-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88-ja310-%D8%AF%D9%82%D8%AA0001%DA%AF%D8%B1%D9%85-%D9%88-%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-310%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/img/favicon.ico?1617621458 | other |
| GET | https://sample.com/balance/js/jquery/plugins/jquery.easing.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/js/modules/blocktopmenu/js/hoverIntent.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/js/products-comparison.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/fonts/droidkufi/DroidKufi-Regular.woff | font |
| GET | https://sample.com/balance/c/3-category_default/%D9%87%D9%85%D9%87-%D8%AA%D8%B1%D8%A7%D8%B2%D9%88%D9%87%D8%A7.jpg | image |
| GET | https://sample.com/balance/modules/productcomments/js/jquery.textareaCounter.plugin.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/css/autoload/highdpi.css | stylesheet |
| GET | https://sample.com/balance/js/jquery/plugins/jquery.scrollTo.js | script |
| GET | https://sample.com/balance/modules/sendtoafriend/sendtoafriend.css | stylesheet |
| GET | https://sample.com/balance/modules/socialsharing/js/socialsharing.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/js/modules/blocktopmenu/js/superfish-modified.js | script |
| GET | https://sample.com/balance/84-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88-gf-32k-%D8%AF%D9%82%D8%AA-01-%DA%AF%D8%B1%D9%85-%D9%88%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-31%DA%A9%DB%8C%D9%84%D9%88%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/themes/default-bootstrap/js/modules/sendtoafriend/sendtoafriend.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/js/modules/sendtoafriend/sendtoafriend.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/js/modules/sendtoafriend/sendtoafriend.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/fonts/droidkufi/DroidKufi-Regular.woff2 | font |
| GET | https://sample.com/balance/themes/default-bootstrap/fonts/droidnaskh/DroidNaskh-Regular.woff | font |
| GET | https://sample.com/balance/themes/default-bootstrap/css/modules/productcomments/productcomments_rtl.css | stylesheet |
| GET | https://sample.com/balance/themes/default-bootstrap/fonts/droidkufi/DroidKufi-Bold.woff | font |
| GET | https://sample.com/balance/modules/productcomments/js/jquery.textareaCounter.plugin.js | script |
| GET | https://sample.com/balance/91-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88%DB%8C-sf400d-%D8%AF%D9%82%D8%AA-01-%DA%AF%D8%B1%D9%85-%D9%88-%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-3000-%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/99-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88-hl1200-%D8%AF%D9%82%D8%AA-01%DA%AF%D8%B1%D9%85-%D9%88-%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-1200%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/92-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88%DB%8C-sature-%D8%AF%D9%82%D8%AA-1-%DA%AF%D8%B1%D9%85-%D9%88-%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-60-%DA%A9%DB%8C%D9%84%D9%88%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/139-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88-hl5000-%D8%AF%D9%82%D8%AA-01%DA%AF%D8%B1%D9%85-%D9%88-%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-5000%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/themes/default-bootstrap/js/global.js | script |
| GET | https://sample.com/balance/210-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88%DB%8C-amput-%D8%AF%D9%82%D8%AA-01-%DA%AF%D8%B1%D9%85-.jpg | image |
| GET | https://sample.com/balance/themes/default-bootstrap/css/modules/blockmyaccountfooter/blockmyaccount.css | stylesheet |
| GET | https://sample.com/balance/85-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88%DB%8C-notebook-%DB%8C%DA%A9%D8%B5%D8%AF%D9%85.jpg | image |
| GET | https://sample.com/balance/js/jquery/plugins/bxslider/jquery.bxslider.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/css/global_rtl.css | stylesheet |
| GET | https://sample.com/balance/themes/default-bootstrap/css/product_list_rtl.css | stylesheet |
| GET | https://sample.com/balance/137-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88-ek2200i-%D8%AF%D9%82%D8%AA001%DA%AF%D8%B1%D9%85-%D9%88-%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-2200%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/themes/default-bootstrap/js/product.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/css/modules/blockuserinfo/blockuserinfo_rtl.css | stylesheet |
| GET | https://sample.com/balance/84-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88-gf-32k-%D8%AF%D9%82%D8%AA-01-%DA%AF%D8%B1%D9%85-%D9%88%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-31%DA%A9%DB%8C%D9%84%D9%88%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/themes/default-bootstrap/js/modules/blocktopmenu/js/hoverIntent.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/css/modules/blocklanguages/blocklanguages_rtl.css | stylesheet |
| GET | https://sample.com/balance/themes/default-bootstrap/fonts/droidkufi/DroidKufi-Regular.woff2 | font |
| GET | https://sample.com/balance/82-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88-ge220-%D8%AF%D9%82%D8%AA0001%DA%AF%D8%B1%D9%85-%D9%88-%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-220%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/js/tools.js | script |
| GET | https://sample.com/balance/themes/default-bootstrap/css/autoload/highdpi.css | stylesheet |
| GET | https://sample.com/balance/73-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88-ek10000-%D8%AF%D9%82%D8%AA-01%DA%AF%D8%B1%D9%85-%D9%88-%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-10%DA%A9%DB%8C%D9%84%D9%88%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/86-home_default/%D8%AA%D8%B1%D8%A7%D8%B2%D9%88%DB%8C-notebook-%D8%AF%D9%82%D8%AA-01-%DA%AF%D8%B1%D9%85-%D9%88-%D8%B8%D8%B1%D9%81%DB%8C%D8%AA-2000-%DA%AF%D8%B1%D9%85.jpg | image |
| GET | https://sample.com/balance/themes/default-bootstrap/fonts/droidkufi/DroidKufi-Bold.woff | font |
لاگ بررسی28
Crawl a new balance page to increase coverage and potentially expose more missing headers or dynamic scripts. Analyze the vulnerable jQuery library already flagged. Verify third‑party domains with medium severity. Retrieve a source map for jquery-migrate to see if it reveals internal code. Check another third‑party domain used for trust seals.
Crawl a new product page to increase page coverage and discover additional assets or vulnerabilities. Analyze wp-embed.min.js which is referenced in a postMessage issue and fetch its source map for deeper code inspection. Check third‑party domains s4.histats.com and t.dtscout.com that have not been examined yet, as they may host tracking or malicious resources.
We need broader page coverage and deeper analysis of flagged issues. Crawling a balance search page adds new content paths. The selectnav.js script is flagged via source‑map exposure; fetching the script and its map may reveal vulnerable code. Remaining unknown third‑party domains (e.dtscout.com and a.mrktmtrcs.net) have not been inspected yet and could host malicious resources.
Crawl a new balance product page to increase page coverage and discover additional resources. Fetch two unexamined theme scripts (placeholders.js and responsive.js) that may contain vulnerable code or expose further third‑party calls. Check two remaining third‑party domains (dtsedge.com and p.mrktmtrcs.net) that have not yet been investigated, as they could be sources of tracking or malicious content. All actions stay within budget and avoid repeats.
We need broader page coverage and deeper script analysis. Selected two yet‑unvisited balance pages to increase surface area, focusing on different query parameters. Added three FETCH_SOURCEMAP actions for remaining theme JS source maps that have not been retrieved, which may expose internal code and further vulnerabilities.
Crawl a product page to verify missing security headers and discover additional resources. Analyze the unexamined scroll-to-top.js for vulnerable patterns. Retrieve the jquery source map to aid deeper JS vulnerability analysis. Re‑check a third‑party domain (e.dtscout.com) to confirm its behavior. Probe a common WordPress AJAX endpoint that may expose further issues.
Continue expanding page coverage by crawling two unvisited product/search pages, analyze the jquery-migrate script which has not been examined yet, re‑analyze a theme script to verify any missed issues, and double‑check a third‑party domain already listed to ensure no new behavior appears.
Crawl additional product pages to discover new scripts, resources, and third‑party domains while staying within the page budget. Fetch a commonly used WordPress script (wp-emoji-release.min.js) that hasn't been analysed yet to check for vulnerable code patterns. Check google-analytics.com as a likely undiscovered third‑party domain that could introduce privacy or security concerns.
We need broader page coverage by crawling two uncovered product pages from the discovered links list, which may reveal additional scripts, endpoints, or third‑party resources. The wp-emoji-release.min.js script has not been analysed yet; fetching it could expose further vulnerable patterns or hidden API calls. Its source map is also untested and may disclose original source code. These actions stay within budget and target high‑value information without repeating previous work.
We need broader page coverage; selecting a new balance product page from the undiscovered links expands the crawl. The wp-emoji-release script hasn't been analysed yet, and may contain additional vulnerable patterns or third‑party calls. No further third‑party domains or source maps are pending, and budget allows these actions.
Crawl a new product page to increase page coverage and discover additional assets. Fetch the jquery-migrate script which hasn't been analysed yet but is flagged as a source map exposure. Check a common third‑party domain (fonts.gstatic.com) that may be loading resources. Attempt to fetch a likely unanalysed custom theme script and its source map to uncover hidden code or vulnerabilities.
Crawl additional product pages to increase page coverage and discover new resources. Fetch two unexamined scripts (wp-emoji-release.min.js and custom.js) that may contain vulnerable patterns or external calls. Check fonts.googleapis.com as a common third‑party CDN not yet investigated.
We need deeper coverage: crawl a new product page to discover more resources, analyze unexamined scripts (wp-emoji-release.min.js and custom.js) for hidden issues, fetch its source map, and verify the Google Fonts domain which is widely used but not yet checked.
Continue expanding page coverage by crawling two uncrawled product pages from the discovered links list, focusing on balance product URLs. Fetch and analyse the wp-emoji-release.min.js script, which has not been examined yet, to identify any hidden vulnerabilities. Check google-analytics.com, a major third‑party domain not yet inspected, for potential data leakage. Finally, attempt to retrieve its source map to aid deeper script analysis.
Add coverage of unscanned product pages to verify missing security headers and potential injection issues. Analyze a new JavaScript file (wp-emoji-release.min.js) that hasn't been inspected for vulnerable patterns. Finally, confirm the security posture of font CDNs (fonts.googleapis.com, fonts.gstatic.com) which are commonly used but not yet checked.
Crawl additional product pages to increase coverage of the large balance catalog. Fetch a new script (wp-emoji-release.min.js) that hasn't been analyzed yet, which may contain hidden issues. Check the common analytics domain google-analytics.com for security posture. Attempt to retrieve its source map to see if debugging info is exposed.
We need broader page coverage, so crawl a new product page from the undiscovered list. Several JavaScript assets remain unanalyzed (wp-emoji-release.min.js and custom.js) and their source maps may reveal more vulnerabilities, so fetch them. A major third‑party analytics provider (google-analytics.com) has not been checked yet, so inspect it. All actions stay within budget and avoid repeats.
Continue expanding page coverage by crawling two unvisited product pages from the discovered links. Analyse a new JavaScript file (wp-emoji-release.min.js) that hasn't been inspected yet, and attempt to fetch its source map (note the typo in the domain for the map URL). Finally, verify a third‑party domain (e.dtscout.com) that appears in resource loads but hasn't been explicitly checked in this run.
Crawl a new product page to increase coverage of the large balance catalog. Analyze custom.js (new script not previously examined) and the wp-emoji-release.min.js script to assess potential vulnerabilities. Check google-analytics.com, a common third‑party domain not yet inspected, for tracking or data leakage. Retrieve the source map for wp-emoji-release.min.js to see if it reveals original source code or secrets.
Continue expanding coverage by crawling additional product pages from the discovered links to uncover more hidden resources and potential issues. Fetch a major script (wp-emoji-release.min.js) that has not been analysed yet. Re‑verify a third‑party domain already flagged to confirm its behavior. Probe the common WordPress REST API endpoint to check for exposed data or misconfigurations.
We need broader page coverage; crawling a new balance product page adds fresh content and may reveal additional scripts or third‑party resources. The wp-emoji-release.min.js script has not been analysed yet and could contain vulnerabilities. Its source map is also unexamined, useful for deeper static analysis. Finally, re‑checking the Google Fonts domains ensures their security headers and CSP compliance, as they are frequently used but not yet verified.
Crawl two deeper product pages to discover additional scripts and third‑party resources. Analyze the theme's custom.js which hasn't been examined yet and may contain vulnerable code. Verify the Google Fonts domain (already in checked list but ensure no missed sub‑resources). Attempt to fetch the source map for custom.js to expose potential client‑side source code.
Continue expanding page coverage by crawling several uncrawled product pages from the discovered links list, focusing on different product categories. Fetch the wp-emoji-release.min.js script which has not yet been analyzed in detail. Finally, verify the Google Fonts domain (fonts.googleapis.com) which is used but not yet checked for security/privacy implications.
No reasoning provided
Crawl two additional product pages to increase page coverage and potentially uncover new issues. Fetch and analyze the custom.js script which hasn't been examined yet and retrieve its source map for deeper inspection. Finally, check the well-known analytics domain to confirm its behavior and any privacy implications.
Select an unvisited product page to increase coverage of the balance section, fetch and analyse custom JavaScript (custom.js) and the emoji script which haven't been examined yet, verify the Google Fonts domain for any issues, and attempt to retrieve the source map for custom.js to detect hidden vulnerabilities.
Continue expanding page coverage by crawling a product detail page to verify if missing security headers and third‑party domains persist across the site. Additionally, fetch and analyse jquery-migrate.min.js, which is flagged as a vulnerable library but has not yet been examined in detail.