CVE-2026-2948
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 · uneditedThe Gutenverse – Ultimate WordPress FSE Blocks Addons & Ecosystem plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 3.5.3 via the import_images() function. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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 confidenceThe Gutenverse WordPress plugin contains an SSRF vulnerability in the import_images() function affecting versions up to 3.5.3. Authenticated users with contributor-level permissions or higher can abuse this to make arbitrary HTTP requests from the server, potentially accessing internal services or exfiltrating data.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Gutenverse plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'gutenverse' or 'gutenverse-core'. If using WP-CLI, run: wp plugin list --name='gutenverse*'Affected if The plugin folder exists in the WordPress installation
-
Identify installed Gutenverse versionRead the plugin header from gutenverse.php or gutenverse-core.php file inside the plugin folder to find the 'Version:' field. Alternatively, use WP-CLI: wp plugin get gutenverse --field=versionAffected if The installed version is 3.5.3 or earlier (any version up to and including 3.5.3)
-
Verify contributor-level or higher users existIn the WordPress admin panel under Users, check for any accounts with the 'Contributor' role. Or query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'contributor'.Affected if There is at least one user account with contributor-level permissions or higher who can access the WordPress admin area
-
Confirm import_images function is present and accessibleSearch the plugin files for the import_images function definition. In the plugin directory, run: grep -r 'function import_images' . --include='*.php'Affected if The import_images() function exists in the plugin code, indicating the vulnerable code path is present
A user is affected if the Gutenverse plugin is installed at version 3.5.3 or earlier AND at least one user with contributor-level or higher access exists on the WordPress site.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the Gutenverse plugin to a version newer than 3.5.3 which contains the patched import_images() function. If an update is unavailable, disable the plugin or restrict contributor-level user capabilities until a fix is released.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-2948 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2948 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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