dbcve.org
Backup SchedulerWordPress extension · Backup Scheduler Project

CVE-2022-38079

HIGH · 8.8 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to after 1.5.13 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability Backup Scheduler plugin <= 1.5.13 at WordPress.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Backup Scheduler WordPress plugin versions 1.5.13 and below allows attackers to trick authenticated administrators into performing unintended actions such as triggering backup operations or modifying plugin settings.

MitigationUpdate the Backup Scheduler plugin to a version above 1.5.13 which includes proper nonce token validation for state-changing operations. As an interim measure, ensure admin sessions are not active while browsing untrusted sites.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Backup SchedulerWordPress extension
Affected:<= 1.5.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Backup Scheduler plugin is installed
    Check WordPress installation for presence of Backup Scheduler plugin in wp-content/plugins directory or via WordPress admin plugin list
    Affected if Plugin is found in the WordPress plugins directory or listed in WP admin panel
  2. Identify installed plugin version
    Read plugin version from backup-scheduler.php header or version constant in the plugin files, or view version in WordPress plugin admin page
    Affected if Version number is 1.5.13 or lower
  3. Verify admin has access to plugin functionality
    Confirm administrator role can access the plugin settings page and trigger backup operations through the WordPress admin dashboard
    Affected if Admin user role can access and interact with plugin features (backup triggers, settings changes)
  4. Check for absence of CSRF protection on state-changing actions
    Examine plugin source code for nonce verification on backup trigger and settings update functions - look for wp_verify_nonce or check_admin_referer calls
    Affected if No nonce validation is performed on admin action functions, allowing unauthenticated requests to trigger operations

Environment is affected if Backup Scheduler plugin version 1.5.13 or lower is installed and the plugin lacks proper nonce validation for admin-triggered actions, enabling attackers to trick logged-in administrators into performing unintended operations via malicious links.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.5.13
Interim mitigation

Update the Backup Scheduler plugin to a version above 1.5.13 which includes proper nonce token validation for state-changing operations. As an interim measure, ensure admin sessions are not active while browsing untrusted sites.

Recommended fix Moderate confidence

1.5.14 or latest available version

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Backup Scheduler plugin
  4. Check if the current version is 1.5.13 or below
  5. If vulnerable, click 'Update Now' to update to the latest version, which should be 1.5.14 or higher
  6. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Backup Scheduler Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38079 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data