Tag: Backup

  • WordPress 7.1.5 Security Release: What It Fixes and How to Update

    WordPress 7.1.5 Security Release: What It Fixes and How to Update

    WordPress 7.1.5 security release graphic: shield with a checkmark over a version badge and 20 security fixes

    Introduction

    WordPress 7.1.5, released on November 18, 2026, is a security release that fixes 20 issues in WordPress core. The most serious is an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution. The WordPress project recommends updating immediately, and it backported the fixes to every branch back to 4.7. CVE IDs are still pending, so this article tracks the official GitHub advisory (GHSA) IDs.

    This article summarizes the official release post, the HelpHub page and the WordPress security advisories. It explains which versions are affected and how to check and update your site. It contains no exploit details.

    Key Facts: WordPress 7.1.5 at a Glance

    • What: WordPress 7.1.5 (November 18, 2026) fixes 20 security issues, including two SQL injections, several cross-site scripting (XSS) flaws and two privilege escalations.
    • Most serious: GHSA-pmp8-6cv8-q323, an unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution. WordPress rates it “high.”
    • Affected: all WordPress versions before 7.1.5, depending on the issue. Fixed backport releases exist for every branch from 7.0 down to 4.7.
    • Severity: 19 GitHub security advisories from the WordPress project: 5 high, 5 medium, 9 low. No CVSS scores were published.
    • CVE IDs: pending. None were assigned or published as of November 22, 2026. The advisories use GHSA IDs only.
    • Exploitation: none reported by WordPress, and no WordPress 7.1.5 issue appears in the CISA KEV catalog (version 2026.11.20, still the latest on November 22, 2026).
    • Action: update to 7.1.5, or to the latest release of your branch (for example 7.0.9 or 6.9.12).

    What Does WordPress 7.1.5 Fix?

    WordPress 7.1.5 fixes 20 security issues, ranging from an unauthenticated privilege escalation to low-risk hardening changes.

    The WordPress project published 19 of them as security advisories in the WordPress/wordpress-develop GitHub repository. The 20th, the removal of the block editor’s Imgur embed variation, is a hardening change without its own advisory.

    AdvisoryIssueWordPress rating
    GHSA-pmp8-6cv8-q323Unauthenticated privilege escalation via Template Part block attributes, possible RCEHigh
    GHSA-cr2m-2j4r-3v3xUnauthenticated stored XSS via shortcode attributes in commentsHigh
    GHSA-mwj7-xhp9-7773Multisite: site Administrator can take over a Super Admin account via Customizer menu previewsHigh
    GHSA-gm52-6h3w-97v4Reflected XSS in the legacy media library popupHigh
    GHSA-jmhp-hg7w-w9c5XSS in the block editor via Openverse image metadataHigh
    GHSA-xc9c-4hg4-h4jgSQL injection in WP_Meta_Query via nested relation valuesMedium
    GHSA-mcv9-c2pg-6m4vSQL injection via the front page setting in Customizer changeset previewsMedium
    GHSA-56j2-5mp6-wr3xUnauthenticated denial of service via batched XML-RPC pingbacksMedium
    GHSA-rcr3-43fx-wqfvUnauthenticated disclosure of private taxonomy terms via the REST API search endpointMedium
    GHSA-p9x8-m3q4-9wg6Subscriber+ information disclosure via XML-RPC wp.getCommentsMedium

    Nine more advisories are rated low. They cover Contributor+ and Administrator XSS issues, Author+ and Editor+ information disclosure, an Author+ authorization bypass in comment editing, and a regular expression hardening fix.

    WordPress 7.1.5 security fixes by WordPress severity rating: 5 high, 5 medium, 9 low, 1 hardening change
    The 20 WordPress 7.1.5 security items by the WordPress project’s own rating.

    What Is the Security Impact?

    The biggest risk is the Template Part privilege escalation, because it can end with an attacker holding an Administrator account.

    How serious is the Template Part privilege escalation?

    The advisory explains that a Template Part block’s theme and slug attributes could make an Administrator’s editor send requests to another URL on the same site. An Author or higher could set these attributes in a post. An unauthenticated attacker could also send an Administrator a crafted editor link. When the Administrator opened it, this could create an Administrator account for the attacker. That account allows code execution through plugin upload.

    So the attack needs an Administrator to open a page in the editor. That is a realistic step, because attackers can hide such links in emails or redirects. The fix was backported to all branches back to 5.9.

    Which other issues matter most?

    The unauthenticated stored XSS in comments matters for any site with open comments. The two SQL injections and the multisite Super Admin takeover matter for sites with many users. The XML-RPC pingback denial of service matters if xmlrpc.php is reachable.

    Which WordPress Versions Are Affected?

    Every branch from 4.7 to 7.1 is affected by some of the 20 issues, and each one has a fixed release.

    BranchFixed releaseIssues that affect the branch
    7.17.1.5All 20
    7.07.0.9All 20
    6.5 to 6.96.5.15, 6.6.12, 6.7.12, 6.8.13, 6.9.12All 20
    6.2 to 6.46.2.16, 6.3.15, 6.4.1519 of 20
    6.0 and 6.16.0.19, 6.1.1718 of 20
    5.95.9.2117 of 20
    5.6 to 5.85.6.24, 5.7.22, 5.8.2015 of 20
    5.1 to 5.55.1.29, 5.2.31, 5.3.28, 5.4.26, 5.5.2513 of 20
    4.8, 4.9, 5.04.8.35, 4.9.36, 5.0.3212 of 20
    4.74.7.4011 of 20
    4.6 and olderNo fixNot supported

    The counts come from the WordPress 7.1.5 HelpHub page. WordPress also says only the most recent version is actively supported, so backports are a courtesy. The same releases remove 1024-bit certificates from the bundled root certificates on 6.9.12 and older. WordPress 7.2 RC 2 includes the fixes as well.

    How Do I Check Whether My Site Needs WordPress 7.1.5?

    Check your exact WordPress version and compare it with the fixed release for your branch.

    How do I check my WordPress version?

    In the admin area, go to Dashboard > Updates. With WP-CLI or shell access, run:

    wp core version
    grep "wp_version =" wp-includes/version.php

    If the result is lower than the fixed release in the table above, your site is affected.

    Are automatic updates already protecting me?

    Possibly. WordPress documentation says existing installations receive minor core updates automatically by default. Check that wp-config.php does not set AUTOMATIC_UPDATER_DISABLED to true or WP_AUTO_UPDATE_CORE to false. Then confirm the version anyway, because hosts and version control setups can block updates.

    How Do I Update to WordPress 7.1.5?

    Update WordPress core from the dashboard or WP-CLI, then confirm the new version.

    1. Back up first. Follow our guide on how to back up WordPress.
    2. Update core. Click Update Now under Dashboard > Updates, or run wp core update.
    3. Stay on an old branch only if you must. Run wp core update --minor to get the latest release of your current branch, such as 6.9.12.
    4. Verify the files. Run wp core verify-checksums to compare core files with the official release.
    5. Update every site. Include staging copies, multisite networks and container images.

    WordPress did not publish a workaround, so updating is the fix.

    Additional Security Recommendations

    WordPress 7.1.5 closes these core flaws, but these steps limit the damage from the next one:

    • Review admin accounts. Remove any Administrator you do not recognize, and use two-factor authentication for every admin.
    • Be careful with editor links. Administrators should not open unexpected editor links from emails or chats.
    • Patch the server stack. Apply the PHP security update and the Apache HTTP Server 2.4.71 or nginx 1.30.7 and 1.31.9 updates.
    • Add a WAF layer. A web application firewall can filter attacks, but it does not replace patching.
    • Update plugins too. An NVD keyword search returned about 200 WordPress-related CVE records published between November 19 and 22, 2026, nearly all for plugins or themes. Keep plugins and themes current.

    FAQ

    Is WordPress 7.1.5 a security release?

    Yes. WordPress calls it a security release and recommends updating immediately. The release post lists 20 security fixes and nothing else for 7.1.5.

    Do the WordPress 7.1.5 vulnerabilities have CVE IDs?

    Not yet; CVE IDs are pending. As of November 22, 2026, the release post, HelpHub page and all 19 GitHub advisories list no CVE IDs, and NVD shows no matching records. Use the GHSA IDs to track them. We will update this article when CVE IDs appear.

    Is anyone exploiting these WordPress flaws?

    WordPress has not reported exploitation, and none of these issues is in the CISA KEV catalog (version 2026.11.20). Public exploit code availability is unknown.

    I run WordPress 6.9. Do I have to move to 7.1?

    No. WordPress 6.9.12 contains fixes for all 20 issues. However, only the latest version is actively supported, so plan the upgrade.

    Conclusion

    WordPress 7.1.5 fixes 20 core security issues, led by a Template Part privilege escalation that can end in code execution. Check your version, install WordPress 7.1.5 or your branch’s backport, and confirm automatic updates are working.

    References

    All links below were checked on November 22, 2026.

    Related Articles

    Last Verified: November 22, 2026. Prepared by SafeWebAcademy from the official WordPress release post, HelpHub page and WordPress security advisories linked above. This is not an official WordPress.org publication. Security details can change, so check the linked advisories for updates.

  • How to Prevent Ransomware Attacks and Stay Safe Online

    How to Prevent Ransomware Attacks and Stay Safe Online

    Ransomware prevention checklist with backups and updates

    Ransomware attacks have become one of the most dangerous online threats for individuals and businesses today. These cyberattacks encrypt your data and demand payment to restore access, often leading to financial loss and downtime. Understanding how to protect your devices and what steps to take can make a huge difference. In this article, we’ll go through effective strategies to prevent ransomware attacks, maintain online safety, and strengthen your cybersecurity defenses.

    Effective Ways to Prevent Ransomware Attacks

    Ransomware spreads through phishing emails, malicious downloads, and software vulnerabilities. To prevent an attack, the first step is to always keep your software and operating system updated. Updates often include patches for security flaws that hackers exploit to install ransomware. Never ignore update notifications; instead, schedule them regularly to ensure your system is protected against the latest threats.

    Another key prevention technique is to back up your data frequently. Store backups offline or on secure cloud services that offer strong encryption. This ensures that even if ransomware infects your device, you’ll be able to restore your files without paying the attackers. Automate your backups where possible to avoid forgetting critical data.

    User awareness is the strongest defense against ransomware. Attackers rely on human error—like clicking suspicious links or downloading unknown attachments—to gain access. Educate yourself and your team to recognize phishing emails, double-check sender addresses, and distrust unsolicited attachments. Cybersecurity training can significantly reduce the risk of a successful attack.

    Best Cybersecurity Tips to Stay Safe Online

    Strong, unique passwords are the foundation of online safety. Use a password manager to create and store complex passwords for every account. Enable multi-factor authentication (MFA) wherever possible to add an additional layer of security that keeps hackers from accessing your data even if they steal your password.

    Avoid public Wi-Fi whenever handling sensitive information. Unsecured networks can allow cybercriminals to intercept your data. If you must use public Wi-Fi, connect through a trusted Virtual Private Network (VPN) to encrypt your traffic. A VPN ensures that your data stays private, even on untrusted networks.

    Keep your devices protected by using reliable antivirus and anti-malware tools. Regularly run scans and monitor for any signs of unusual activity. Many modern operating systems include built-in security features, but investing in a premium cybersecurity suite provides additional real-time protection against ransomware, keyloggers, and other threats.

    Protect Your Devices from Hackers and Malware

    One simple but powerful method to protect your devices is to disable macro scripts in Microsoft Office and other applications. Ransomware often hides in macro-enabled files sent through email attachments. Blocking these macros prevents automated scripts from running malicious code on your system.

    Regularly review your network permissions. Only allow trusted applications, users, and devices to connect. Setting up a firewall and intrusion detection system helps monitor and filter incoming traffic, quickly identifying suspicious behavior. Network segmentation also ensures that if one part of your system is breached, the rest remains safe.

    If you use smart devices or IoT gadgets, always change default usernames and passwords. Smart devices are common entry points for hackers when left unsecured. Keep their firmware updated and restrict remote access features when not needed. The fewer points of vulnerability, the lower your chance of being attacked.

    Q&A: Common Questions About Ransomware

    What should I do if I’m attacked by ransomware?
    Do not pay the ransom. Instead, disconnect from all networks, report the incident to cybersecurity authorities, and contact a professional recovery service. Then, restore your data from secure backups.

    Can antivirus software stop ransomware?
    Yes, many modern antivirus programs can detect and block ransomware before it encrypts your files. However, no solution is 100% foolproof, so combining antivirus protection with good habits is essential.

    Is ransomware prevention expensive?
    Not necessarily. Many effective security measures, such as regular updates, backups, and cybersecurity training, cost little or nothing but provide strong protection against ransomware attacks.

    Ransomware prevention starts with awareness, preparation, and proactive protection. By keeping your systems updated, training yourself and your team, and using strong cybersecurity tools, you can minimize risks and safeguard your digital life. Staying vigilant and ready is the best way to stay safe from evolving cyber threats and keep your data secure online.

    Related reading

  • How to back up WordPress

    How to back up WordPress

    WordPress site backup of files and database to remote storage

    Update note (November 2026): WordPress 7.1.5 is a security release with fixes backported to older branches. Take a full backup of your files and database before you update, then update as soon as possible.

    Why Backing Up a WordPress Site is Essential

    To back up WordPress properly, you need a copy of both the database and the site files. The official WordPress documentation on backups explains why: the database holds every post, comment and link on your site, and if it is erased or corrupted you could lose everything you have written. Hacks, failed updates, crashes and mistakes can all force a rollback.

    This guide covers the files, the database, safe storage, automation and restore testing.

    What a complete WordPress backup includes

    • The database: posts, pages, comments, users and settings, stored in MySQL or MariaDB, not in the site folder.
    • The files: WordPress core, themes, plugins, media uploads, wp-config.php and .htaccess.

    WordPress recommends treating both as one backup set, made around the same time: export the database first, then copy the files.


    How Often Should You Back Up WordPress?

    The WordPress documentation suggests weekly backups for smaller sites and daily backups for busy ones. It also says to back up always before an upgrade or a move to a new host, and to keep at least 3 to 5 recent backups in different locations.

    Treat every core, plugin and theme update the same way. Updates fix security issues, so install them promptly, but they can also break a site. Take a fresh backup, check that it is not empty, then click Update.


    Follow the 3-2-1 Backup Rule

    CISA, the US Cybersecurity and Infrastructure Security Agency, recommends the 3-2-1 backup rule: 3 copies of important files, on 2 different types of storage (such as a hard drive and the cloud), with 1 copy kept off-site.

    For WordPress, that could be the live site, a cloud or backup-server copy, and a copy on an external drive. Keep at least one copy offline. CISA’s #StopRansomware Guide warns that ransomware actors try to delete or encrypt any backups they can reach, and that automated cloud sync alone may copy encrypted files over good ones.


    How to Back Up WordPress Step by Step

    These commands assume a Linux server with WordPress in /var/www/html. Adjust paths and names to suit.

    Step 1: Backup WordPress Files

    WordPress files include themes, plugins, and media uploads, typically stored in /var/www/html. Use the following command to back them up:

    sudo tar -czvf wordpress-files-backup.tar.gz /var/www/html
    

    This creates a compressed file named wordpress-files-backup.tar.gz.


    Step 2: Backup the WordPress Database

    WordPress uses a MySQL or MariaDB database to store content and settings. Export it with mysqldump, using a dedicated backup user instead of the root account.

    First, create a user that can only read the WordPress database. Run these commands in the MySQL shell and choose your own long, random password:

    CREATE USER 'wp_backup'@'localhost' IDENTIFIED BY 'use-a-long-random-password';
    GRANT SELECT, SHOW VIEW, TRIGGER ON wordpress_db.* TO 'wp_backup'@'localhost';

    Then run the export. Replace wordpress_db with your database name. You will be prompted for the backup user’s password:

    mysqldump -u wp_backup -p --single-transaction --no-tablespaces wordpress_db > wordpress-db-backup.sql

    The privileges above are the minimum mysqldump needs for this command. Using –single-transaction avoids the need to lock tables on InnoDB tables, and –no-tablespaces avoids the need for the PROCESS privilege.


    Step 3: Store Backups Securely

    Never leave backup archives in the web root (/var/www/html). Anyone who guesses the file name might download your database and wp-config.php, which holds your database credentials. Keep backups outside the web root, readable only by your backup user.

    Encrypt backups before they leave the server, as CISA recommends. GnuPG asks for a passphrase and creates an encrypted .gpg copy of each file:

    gpg --symmetric --cipher-algo AES256 wordpress-files-backup.tar.gz
    gpg --symmetric --cipher-algo AES256 wordpress-db-backup.sql

    Keep the passphrase in a password manager, not on the server. Then copy the backups to a separate backup server or cloud storage:

    scp wordpress-files-backup.tar.gz.gpg wordpress-db-backup.sql.gpg user@remote-server:/path/to/backup/
    

    Step 4: Automate WordPress Backups

    To make backups regular, set up a cron job. Never put the database password in the cron command: anyone who can list running processes may see it, and it is stored in plain text in your crontab. Store it in a protected option file instead.

    Create the option file in the home directory of the user that runs the job, and restrict it so only that user can read it:

    nano ~/.wp-backup.cnf
    chmod 600 ~/.wp-backup.cnf

    Put the following in the file:

    [client]
    user=wp_backup
    password=use-a-long-random-password

    Open the crontab editor with crontab -e (use sudo crontab -e if your user cannot read every file in /var/www/html). Add the following lines to back up the files and the database daily. Use the full path to the option file instead of ~, because the shell does not expand a ~ that follows an equals sign:

    0 2 * * * tar -czvf /path/to/backup/wordpress-files-$(date +\%F).tar.gz /var/www/html
    5 2 * * * mysqldump --defaults-file=/home/youruser/.wp-backup.cnf --single-transaction --no-tablespaces wordpress_db > /path/to/backup/wordpress-db-$(date +\%F).sql

    The backslash before % is required, because cron treats an unescaped % as a newline. Backups contain user data, so also store them in a folder that only your backup user can read.


    CISA advises being able to roll back at least seven days, so keep a few weeks of daily backups. Before adding a cleanup job, run it with -print to list what it would remove:

    find /path/to/backup -name "wordpress-*" -mtime +30 -print

    Restoring a WordPress Site

    WordPress recommends restoring the files first, then the database. If database credentials changed, update wp-config.php to match. Follow these steps:

    1. Extract the WordPress files backup: sudo tar -xzvf wordpress-files-backup.tar.gz -C /
    2. Import the database backup using an account that is allowed to create and change tables: mysql -u root -p wordpress_db < wordpress-db-backup.sql
    3. Reset file permissions. WordPress recommends 755 for directories and 644 for files: sudo find /var/www/html -type d -exec chmod 755 {} \; and sudo find /var/www/html -type f -exec chmod 644 {} \;. Set ownership with sudo chown -R www-data:www-data /var/www/html.

    Test your restores

    Test a restore on a staging site now and then. A backup you have never restored is not proven to work. CISA advises testing full and partial restores and documenting the steps.

    • Restore the latest backup set to a staging server.
    • Check that pages, media and the admin dashboard load.
    • Note how long it took and fix any unclear step.

    Should You Use a Backup Plugin or Your Host’s Backups?

    You do not have to use the command line. WordPress documentation points to backup plugins in the Plugin Directory and to backup tools most hosts provide. It notes that getting a copy from your host can take time, and suggests an occasional manual backup to confirm automated ones work. Keep at least one copy outside your hosting account.


    By following this guide, you can recover your WordPress site quickly when something goes wrong. For a more comprehensive guide on backing up an entire server, check out our Ubuntu Server Backup Guide.


    References

    Last verified: 21 November 2026.

    Related reading