LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28036: WordPress Ratatouille theme <= 1.2.6 - Server Side Request Forgery (SSRF) vulnerability

Server-Side Request Forgery (SSRF) vulnerability in SkatDesign Ratatouille ratatouille allows Server Side Request Forgery.This issue affects Ratatouille: from n/a through <= 1.2.6.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-28036 is a medium-severity SSRF issue in the WordPress Ratatouille theme from SkatDesign, affecting versions through 1.2.6. An authenticated attacker with low privileges may be able to make the server send unintended requests. Business risk is mainly internal service exposure or limited data integrity/confidentiality impact.

Executive priority

Treat as a near-term remediation item for WordPress environments using Ratatouille. It is not currently evidenced as actively exploited, but SSRF can create meaningful risk if the web server has access to internal systems.

Technical view

The vulnerability is classified as CWE-918 Server-Side Request Forgery. CVSS 3.1 is 6.4: network exploitable, low complexity, low privileges required, no user interaction, scope changed, low confidentiality and integrity impact, no availability impact. The public record identifies Ratatouille theme versions up to and including 1.2.6 as affected.

Likely exposure

Exposure is limited to WordPress sites using the SkatDesign Ratatouille theme at version 1.2.6 or earlier. Exploitation requires some level of authenticated access, according to the CVSS privileges-required metric.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not listed as CISA KEV in the source bundle. The issue could matter more on sites where the WordPress server can reach sensitive internal services or metadata endpoints.

Researcher notes

The public data is sparse. CVSS indicates authenticated, low-complexity SSRF with changed scope and limited confidentiality/integrity impact. The bundle does not name a fixed version, patch commit, affected endpoint, or proof-of-concept, so validation should focus on asset identification and vendor advisory tracking.

Mitigation direction

  • Inventory WordPress sites for the Ratatouille theme and version.
  • Prioritize sites running Ratatouille 1.2.6 or earlier.
  • Check Patchstack and vendor guidance for an updated version or official workaround.
  • Restrict unnecessary outbound server requests where operationally feasible.
  • Review low-privilege WordPress accounts and remove unnecessary access.

Validation and detection

  • Confirm whether the Ratatouille theme is installed and active.
  • Record the installed theme version across all WordPress environments.
  • Review web server logs for unusual outbound request patterns.
  • Check whether the server can reach sensitive internal-only services.
  • Monitor Patchstack and CVE updates for remediation details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-28036 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2026-28036Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SkatDesignRatatouilleratatouille, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.