SSRF (Server-Side Request Forgery) in ThemeREX Addons (CVE-2026-102797)
Summary
SSRF in ThemeREX Addons (CVE-2026-102797). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Server-Side Request Forgery (SSRF) vulnerability in ThemeREX Group ThemeREX Addons trx_addons allows Server Side Request Forgery.This issue affects ThemeREX Addons: from n/a through 2.46.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-102797 has been found in ThemeREX Addons.
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "ThemeREX Addons CVE-2026-102797" on the vendor's site.
CVE-2026-102797 (ThemeREX Addons) — CWE-918 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in ThemeREX Addons.
Check the vendor advisory for the affected versions of ThemeREX Addons.
Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで ThemeREX Addons を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web patchstack.com
- web nvd.nist.gov
- web github.com