CVE-2022-0255

Database Backup for WordPress <= 2.5 - Admin+ SQL Injection

2022-01-24 00:00

Strategic Overview

Status: Patched in 2.5.1
Affected Plugin: Database Backup for WordPress
Affected Version: < 2.5.1
CVSS: 7.2High
Weakness type: CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE: CVE-2022-0255

View all Database Backup for WordPress vulnerabilities

At a glance

CVE-2022-0255 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Database Backup for WordPress WordPress plugin, affecting versions < 2.5.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.5.1; sites on affected versions should update now. Disclosed January 2022, reported by ZhongFu Su.

Vulnerability Overview

The Database Backup for WordPress plugin before 2.5.1 does not properly sanitise and escape the fragment parameter before using it in a SQL statement in the admin dashboard, leading to an SQL injection issue

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in Database Backup for WordPress < 2.5.1 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Database Backup for WordPress the fix is 2.5.1: builds < 2.5.1 are affected, anything from 2.5.1 onward is not.

Remediation

Update to version 2.5.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Database Backup for WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Database Backup for WordPress 2.5.1 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-0255 https://www.wordfence.com/threat-intel/vulnerabilities/id/4062f981-a1d2-4e54-8fd9-f8855af0a7db https://nvd.nist.gov/vuln/detail/CVE-2022-0255

Related records

Other vulnerabilities in Database Backup for WordPress

CVSS Vector

7.2

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredHigh
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/