Security readout for executives and security teams
Plain-English summary
CVE-2025-32482 affects the WordPress Custom Smilies plugin through version 1.2. A forged request could lead to stored cross-site scripting, meaning malicious script could be saved and later run in a user’s browser. The sources do not name a fixed version or confirm exploitation in the wild.
Executive priority
Treat this as a high-priority WordPress plugin risk, especially for public sites where administrative sessions are frequent. The business concern is stored browser-side compromise, not direct server takeover. Act quickly, but base remediation on confirmed vendor or Patchstack guidance.
Technical view
The CVE describes CWE-352 CSRF in quanganhdo Custom Smilies, package custom-smilies, allowing stored XSS. CVSS 3.1 is 7.1 high with network attack vector, low complexity, no attacker privileges, required user interaction, and changed scope. Evidence does not specify the vulnerable endpoint, required victim role, or patch version.
Likely exposure
Exposure is limited to WordPress sites using the Custom Smilies plugin at version 1.2 or earlier. The bundle lists Custom Smilies as affected through <= 1.2, but does not provide install prevalence, CPEs, or hosting-specific indicators.
Exploitation context
The CVE is not listed as KEV in the provided bundle. The CVSS vector indicates remote attackability with victim interaction, but the sources do not support a claim of active exploitation or provide public exploit evidence.
Researcher notes
Source detail is sparse. The record confirms CSRF to stored XSS and CVSS 7.1, but omits endpoint, nonce behavior, victim role, exploit maturity, and fixed version. Validate exposure by plugin presence and version rather than broader WordPress assumptions.
Mitigation direction
- Inventory WordPress sites for the custom-smilies plugin and version.
- Check Patchstack and vendor guidance for a fixed release or official mitigation.
- Disable or remove the plugin where no confirmed fixed version is available.
- Prioritize sites with many administrators, editors, or exposed login workflows.
Validation and detection
- Confirm whether each WordPress site runs Custom Smilies <= 1.2.
- Review plugin configuration for unexpected stored content or script-like entries.
- Check WordPress admin activity for suspicious recent changes.
- Do not assert active exploitation unless new KEV or vendor evidence appears.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2025-32482 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/custom-smilies/vulnerability/wordpress-custom-smilies-plugin-1-2-csrf-to-stored-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.