LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54672: WordPress Photo Engine Plugin plugin <= 6.4.3 - Cross Site Request Forgery (CSRF) Vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Jordy Meow Photo Engine wplr-sync allows Cross Site Request Forgery.This issue affects Photo Engine: from n/a through <= 6.4.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-54672 is a CSRF issue in the WordPress Photo Engine plugin, package wplr-sync, reported as affecting versions through 6.4.3. An attacker would need a site user to take an action, and the recorded impact is limited to integrity, not data disclosure or availability.

Executive priority

Treat this as a moderate WordPress plugin risk. It should be handled through normal vulnerability management, prioritized for sites with administrative users and internet exposure, but the provided evidence does not support emergency action or active-exploitation claims.

Technical view

The source bundle identifies CWE-352 Cross-Site Request Forgery with CVSS 3.1 score 4.3, vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. The record indicates network reachability and required user interaction, with low integrity impact only. Affected metadata is sparse, but the description states Photo Engine <= 6.4.3.

Likely exposure

Exposure is likely limited to WordPress sites that have the Photo Engine plugin, wplr-sync package, installed at version 6.4.3 or earlier. Sites without this plugin are not indicated as affected by the provided sources.

Exploitation context

The bundle does not show CISA KEV listing and provides no cited evidence of active exploitation. The attack class requires user interaction, consistent with CSRF, and the CVSS record indicates no confidentiality or availability impact.

Researcher notes

The main uncertainty is affected-version metadata: the narrative says Photo Engine through 6.4.3, while the structured affected entry is sparse. Do not infer a patch version from this bundle. Validate against the CVE record, Patchstack entry, and vendor release information.

Mitigation direction

  • Inventory WordPress sites for Photo Engine or wplr-sync plugin usage.
  • Confirm installed plugin versions, especially 6.4.3 or earlier.
  • Check vendor or Patchstack guidance for a fixed release or official mitigation.
  • Prioritize updating affected plugins once an official fixed version is confirmed.
  • Restrict administrative access and review suspicious plugin-setting changes.

Validation and detection

  • Verify whether Photo Engine or wplr-sync is installed on each WordPress site.
  • Record the exact installed plugin version for affected assets.
  • Compare findings with the CVE and Patchstack advisory scope.
  • Check logs or audit trails for unexpected plugin configuration changes.
  • Document any compensating controls pending vendor guidance.
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-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2025-54672 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
4.3 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2025-54672Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
Jordy MeowPhoto Enginewplr-sync, 0unaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

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