Security readout for executives and security teams
Plain-English summary
CVE-2025-23842 affects the WordPress Gallery Plugin by Nilesh Shiragave through version 1.4. A malicious site could abuse a logged-in user’s browser to make unauthorized changes that result in stored cross-site scripting. For a business, this matters when the plugin is installed on public WordPress sites.
Executive priority
Treat as a high-priority WordPress plugin exposure for affected sites, especially public marketing or customer-facing sites. Prioritize inventory first, then update or disable the plugin based on vendor guidance.
Technical view
The source bundle describes a CSRF weakness in wordpress-gallery-plugin that can lead to stored XSS. CVSS 3.1 is 7.1 high with network attack vector, low complexity, no attacker privileges, and required user interaction. The supplied affected metadata is limited and partly inconsistent, but the description and reference name versions through 1.4.
Likely exposure
Exposure is likely limited to WordPress sites running Nilesh Shiragave WordPress Gallery Plugin, package wordpress-gallery-plugin, at version 1.4 or earlier. Sites not using this plugin are not indicated as affected by the supplied sources.
Exploitation context
The bundle does not report CISA KEV listing or active exploitation. The risk depends on an attacker inducing user interaction and the vulnerable plugin accepting a forged request that stores script content for later execution.
Researcher notes
Evidence is sparse: the source bundle identifies CSRF to stored XSS and CVSS details, but does not include proof-of-concept status, exploit telemetry, or a named fixed version. Avoid assuming broad WordPress impact beyond this specific plugin.
Mitigation direction
Inventory WordPress sites for wordpress-gallery-plugin and confirm installed versions.
Check vendor or Patchstack guidance for a fixed release or official mitigation.
Upgrade if an official fixed version is available.
Disable or remove the plugin if no maintained fix is available.
Limit administrative sessions and use CSRF protections where configurable.
Validation and detection
Confirm whether the plugin is installed on each WordPress site.
Record plugin version and flag version 1.4 or earlier.
Review plugin pages and stored gallery content for unexpected script-like entries.
Check WordPress audit logs for suspicious plugin configuration changes.
Monitor vendor and Patchstack entries for updated remediation details.
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.
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.
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.