dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2023-50374

MEDIUM · 5.5 CVSS v3.1 Published 2024-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Server-Side Request Forgery (SSRF) vulnerability in NiteoThemes CMP – Coming Soon & Maintenance.This issue affects CMP – Coming Soon & Maintenance: from n/a through 4.1.10.

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

Server-Side Request Forgery (SSRF) vulnerability in NiteoThemes CMP plugin allows remote attackers to induce the server to make arbitrary requests to internal or external resources by manipulating input that controls URL fetching. The vulnerability exists in versions up to and including 4.1.10, potentially allowing enumeration of internal services or exfiltration of data via the compromised server.

MitigationUpdate CMP – Coming Soon & Maintenance to the latest version once available and implement strict allow-listing for any user-controlled URL parameters to prevent requests to internal network resources.

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

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
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 CMP plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > look for 'CMP - Coming Soon & Maintenance' or 'NiteoThemes CMP' and check the version number displayed, or inspect the plugin's main PHP file (e.g., /wp-content/plugins/cmp-coming-soon-maintenance/*.php) for the 'Version' header comment
    Affected if Version is 4.1.10 or lower
  2. Confirm CMP plugin is active
    In WordPress admin > Plugins, verify the CMP plugin status shows as 'Active'
    Affected if Plugin is active and version is vulnerable
  3. Check for URL-based features enabled
    Go to CMP plugin settings pages (usually under Settings > Coming Soon or CMP in the admin menu) and look for any fields that accept URLs, such as custom logo URLs, background image URLs, external resource links, or any 'fetch from URL' options
    Affected if Any URL input fields are available or configured in the plugin settings
  4. Inspect HTTP request logging if available
    Review server access logs (Apache/Nginx) for unusual outgoing requests from the web server to internal IP ranges (e.g., 10.x.x.x, 192.168.x.x, 127.0.0.1) or unexpected external domains that coincide with CMP plugin activity or configuration saves
    Affected if Outgoing requests from the server to internal/private network addresses are present in logs

You are affected if the CMP plugin version is 4.1.10 or lower and the plugin is active with any URL-fetching functionality accessible or configured.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update CMP – Coming Soon & Maintenance to the latest version once available and implement strict allow-listing for any user-controlled URL parameters to prevent requests to internal network resources.

Recommended fix Moderate confidence

Version 4.1.11 or later (upgrade to the latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'CMP – Coming Soon & Maintenance' by NiteoThemes
  4. Check the current version number to confirm it is 4.1.10 or below
  5. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository and upload it
  6. Verify the update was successful by checking the plugin version after updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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