dbcve.org
Seraphinite Post .docx SourceWordPress extension · S Sols

CVE-2024-38728

MEDIUM · 6.4 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 2.16.10 or later.
See remediation →
70/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 Seraphinite Solutions Seraphinite Post .DOCX Source.This issue affects Seraphinite Post .DOCX Source: from n/a through 2.16.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 · moderate confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in the Seraphinite Post .DOCX Source WordPress plugin. The vulnerability allows an attacker to make the affected server perform arbitrary HTTP requests to internal or external resources, potentially exposing internal services, bypassing network segmentation, or retrieving sensitive data from cloud metadata endpoints.

MitigationUpgrade to version 2.16.9 or later. Additionally, implement input validation with strict allowlists for any user-controlled URL parameters, disable unnecessary URL protocols, and ensure proper network segmentation to limit the impact of SSRF attacks.

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
Seraphinite Post .docx SourceWordPress extension
Affected:< 2.16.10

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify the plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'Seraphinite Post .docx Source' in the list, or check the /wp-content/plugins/ directory for a folder containing 'seraphinite' or 'post-docx-source'
    Affected if the plugin folder exists in the WordPress plugins directory
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find the Seraphinite Post .docx Source plugin, and view the version number displayed beneath the plugin name. Alternatively, open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if the version number is less than 2.16.10 (for example, 2.16.9, 2.16.8, etc.)
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that Seraphinite Post .docx Source shows as 'Active' under the plugin status
    Affected if the plugin is both installed and currently activated on the site
  4. Identify if URL-based features are in use
    Review the plugin settings pages (under Settings or a dedicated plugin menu) for any options that accept URLs as input, such as document import URLs, external resource fetching, or content retrieval endpoints. Check page source for any forms or AJAX handlers that accept URL parameters
    Affected if the plugin has configuration options or features that accept external URLs and the plugin version is below 2.16.10

A user is affected if the Seraphinite Post .docx Source plugin version is below 2.16.10 and the plugin is installed and active on their WordPress site.

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

Upgrade to version 2.16.9 or later. Additionally, implement input validation with strict allowlists for any user-controlled URL parameters, disable unnecessary URL protocols, and ensure proper network segmentation to limit the impact of SSRF attacks.

Recommended fix High confidence

2.16.10 or later

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Seraphinite Post .DOCX Source in the plugin list
  4. Click 'Update Now' if an update is available, or manually update to version 2.16.10 or later
  5. Verify the plugin version after updating to confirm version 2.16.10 or higher is installed
  6. Test the plugin functionality to ensure the update was successful and didn't break existing features

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

Fix this in Seraphinite Post .docx Source Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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