dbcve.org
Ultimate Coming Soon \& MaintenanceApplication · Rstheme

CVE-2025-24546

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
61/100
Remediation priority · Elevated
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 in RSTheme Ultimate Coming Soon & Maintenance ultimate-coming-soon allows Cross Site Request Forgery.This issue affects Ultimate Coming Soon & Maintenance: from n/a through <= 1.0.9.

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 · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the RSTheme Ultimate Coming Soon & Maintenance WordPress plugin (ultimate-coming-soon <= 1.0.9) allows attackers to trick authenticated administrators into performing unintended actions via maliciously crafted requests, such as modifying maintenance page settings or toggling the coming soon mode.

MitigationAdd WordPress nonce verification to all form submissions and AJAX actions in the plugin, validate the nonce server-side before processing any state-changing requests, and implement SameSite cookie attributes.

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
Ultimate Coming Soon \& MaintenanceApplication
Affected:< 1.1.0

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
None
Integrity
Low
Availability
Low

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

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. Check if RSTheme Ultimate Coming Soon plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'RSTheme Ultimate Coming Soon & Maintenance' or check the wp-content/plugins directory for a folder containing 'ultimate-coming-soon' or 'rstheme' in the name
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find the RSTheme Ultimate Coming Soon plugin, and note the version number displayed
    Affected if The version is 1.0.9 or lower (any version before 1.1.0)
  3. Inspect plugin source code for nonce verification
    Access the plugin PHP files via file manager or FTP, locate form handlers and AJAX action callbacks (typically in main plugin file or includes/admin folder), and search for 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' function calls
    Affected if Form processing or AJAX action handlers lack nonce verification calls
  4. Check for SameSite cookie attributes
    Examine the plugin code for Set-Cookie headers or WordPress cookie setting functions to see if SameSite attribute is configured
    Affected if Cookies are set without SameSite attribute on maintenance page functions

A user is affected if the RSTheme Ultimate Coming Soon & Maintenance plugin version 1.0.9 or lower is installed and the plugin handles admin actions without verifying nonces or using SameSite cookies.

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 1.1.0 or later
Fixed in 1.1.0
Interim mitigation

Add WordPress nonce verification to all form submissions and AJAX actions in the plugin, validate the nonce server-side before processing any state-changing requests, and implement SameSite cookie attributes.

Recommended fix High confidence

1.1.0

  1. Backup your WordPress site before making any changes
  2. Update the Ultimate Coming Soon & Maintenance plugin to version 1.1.0 or later through the WordPress admin dashboard (Plugins > Installed Plugins > Update Now)
  3. Verify the plugin update was applied successfully by checking the plugin version
  4. Test the coming soon/maintenance functionality to ensure the plugin continues to work correctly after the update

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

Fix this in Ultimate Coming Soon \& Maintenance Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24546 — 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-2025-24546 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