LiveActive security incident?Get immediate response
CVE Record

CVE-2025-46512: WordPress Custom Functions Plugin plugin <= 1.1 - CSRF to Stored XSS vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Shamim Hasan Custom Functions Plugin custom-functions allows Stored XSS.This issue affects Custom Functions Plugin: from n/a through <= 1.1.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability can let an attacker trick a logged-in WordPress user into making an unintended change that results in stored cross-site scripting. Stored XSS can persist on the site and affect later visitors or administrators. The source data does not name a fixed version or confirm exploitation in the wild.

Executive priority

Treat as high priority for affected WordPress sites, especially public sites or sites managed by multiple administrators. Prioritize inventory, containment, and vendor guidance because the sources do not identify a confirmed patch.

Technical view

CVE-2025-46512 affects Shamim Hasan Custom Functions Plugin custom-functions through version 1.1. It is listed as CWE-352 CSRF leading to stored XSS, CVSS 3.1 score 7.1, network exploitable with low complexity and required user interaction. Privileges are listed as none for the attacker.

Likely exposure

Exposure is limited to WordPress sites with Custom Functions Plugin custom-functions installed at version 1.1 or earlier. The bundle does not provide install prevalence, vulnerable endpoint details, or a confirmed fixed version.

Exploitation context

CISA KEV is false in the provided bundle, and no cited source confirms active exploitation. The attack model requires user interaction, consistent with CSRF, and could produce persistent script execution if successful.

Researcher notes

The public bundle identifies CSRF to stored XSS but omits endpoint, nonce behavior, role prerequisites, exploit maturity, and remediation version. Avoid assuming a patch exists. Validate exposure through asset inventory and controlled defensive review only.

Mitigation direction

  • Inventory WordPress sites for custom-functions version 1.1 or earlier.
  • Check Patchstack and vendor guidance for a fixed release or official mitigation.
  • Disable or remove the plugin where business impact allows until guidance is available.
  • Apply least-privilege administration and avoid browsing untrusted links while logged into WordPress.

Validation and detection

  • Confirm whether the Custom Functions Plugin is installed on each WordPress property.
  • Record installed plugin version and compare against affected versions through 1.1.
  • Review WordPress content and admin areas for unexpected stored script content.
  • Check security logs for suspicious plugin configuration changes around administrator sessions.
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-46512 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
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

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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-46512Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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
Shamim HasanCustom Functions Plugincustom-functions, 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.