dbcve.org
SpectraWordPress extension · Brainstormforce

CVE-2023-36679

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to 2.6.7 or later.
See remediation →
71/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 Brainstorm Force Spectra.This issue affects Spectra: from n/a through 2.6.6.

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 the Brainstorm Force Spectra WordPress plugin allows attackers to make the server perform unintended requests to internal or external resources. This can lead to exposure of internal services, network scanning, or bypassing security boundaries.

MitigationUpdate Spectra plugin to the latest version beyond 2.6.6 to receive the security patch. If immediate update is not possible, restrict access to the affected plugin endpoints through web application firewall rules or network segmentation.

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
SpectraWordPress extension
Affected:< 2.6.7

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Spectra plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Spectra' or 'Ultimate Addons for Gutenberg' by Brainstorm Force. Alternatively, check the /wp-content/plugins/ directory for a folder named 'spectra' or similar.
    Affected if The plugin is not found or not installed
  2. Check installed Spectra version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the Spectra plugin. Alternatively, check the main plugin file header in /wp-content/plugins/spectra/includes/ or similar path for 'Version:' declaration.
    Affected if Version is less than 2.6.7 or the version cannot be determined (uninstalled plugin is not affected)
  3. Identify accessible plugin endpoints
    Check web server access logs (Apache: /var/log/apache2/access.log, Nginx: /var/log/nginx/access.log) or WordPress debug logs for requests to plugin AJAX handlers or API endpoints. Common paths include /wp-admin/admin-ajax.php or /wp-json/ with 'spectra' or 'uag' in the request URI.
    Affected if Requests to Spectra-related endpoints are being served (indicates the plugin is active and processing requests)
  4. Review outbound server requests
    Inspect web server logs or use network monitoring (tcpdump, Wireshark) to identify if the server has made unexpected outbound HTTP/HTTPS requests to internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x) or unusual external domains originating from the WordPress site.
    Affected if Unexpected outbound requests are observed from the web server

A user is affected if the Spectra plugin is installed with a version lower than 2.6.7 and the plugin's request-handling endpoints are accessible on the server.

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.6.7 or later
Fixed in 2.6.7
Interim mitigation

Update Spectra plugin to the latest version beyond 2.6.6 to receive the security patch. If immediate update is not possible, restrict access to the affected plugin endpoints through web application firewall rules or network segmentation.

Recommended fix Moderate confidence

Spectra 2.6.7

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Locate the Spectra plugin
  4. Update Spectra to version 2.6.7 or later
  5. Verify the update was successful by confirming the installed version

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

Fix this in Spectra Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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