LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24381: WordPress PhotoMe theme < 5.7.2 - Server Side Request Forgery (SSRF) vulnerability

Server-Side Request Forgery (SSRF) vulnerability in ThemeGoods PhotoMe photome allows Server Side Request Forgery.This issue affects PhotoMe: from n/a through < 5.7.2.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24381 affects the WordPress PhotoMe theme before version 5.7.2. It is a server-side request forgery issue, meaning a remote attacker may be able to make the website server send requests to unintended locations. The public record rates it medium severity, and there is no cited evidence of active exploitation.

Executive priority

Treat this as a moderate-priority web application risk. Prioritize internet-facing WordPress sites using PhotoMe, especially those handling sensitive content or deployed in networks with valuable internal services reachable from the web server.

Technical view

The issue is categorized as CWE-918 SSRF in ThemeGoods PhotoMe versions earlier than 5.7.2. CVSS 3.1 is 5.4: network exploitable, high attack complexity, no privileges or user interaction required, changed scope, and low confidentiality and integrity impact. Availability impact is listed as none.

Likely exposure

Exposure is limited to WordPress sites using the ThemeGoods PhotoMe theme below 5.7.2. Sites not using this theme, or already on 5.7.2 or later, are not indicated as affected by the provided sources.

Exploitation context

The CVE record says exploitation is network-accessible and requires no authentication, but attack complexity is high. The source bundle does not include exploit details, proof-of-concept code, or reports of active exploitation. CISA KEV status is false in the provided data.

Researcher notes

Public details are sparse. The CVE and Patchstack entry identify SSRF in PhotoMe before 5.7.2, but do not provide enough information here to assess specific vulnerable endpoints, prerequisites beyond CVSS, or practical exploitability. Avoid assuming active exploitation without additional evidence.

Mitigation direction

  • Inventory WordPress sites for the ThemeGoods PhotoMe theme.
  • Upgrade PhotoMe to version 5.7.2 or later where applicable.
  • If upgrading is not possible, check ThemeGoods or Patchstack guidance for supported mitigations.
  • Reduce unnecessary outbound server access where operationally feasible.

Validation and detection

  • Confirm whether PhotoMe is installed on each WordPress site.
  • Record the installed PhotoMe version and compare it with 5.7.2.
  • Review vulnerability management tools for CVE-2026-24381 detections.
  • Verify remediation by confirming the theme version after update.
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-24381 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
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N2.22.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/PR:N/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
ThemeGoodsPhotoMephotome, 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.