dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-39530

HIGH · 7.1 CVSS v3.1 Published 2025-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in dsky Site Search 360 site-search-360 allows Stored XSS.This issue affects Site Search 360: from n/a through <= 2.1.8.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in Site Search 360 allows authenticated users to unknowingly execute malicious requests that inject persistent malicious scripts (Stored XSS) into the search application. The lack of proper CSRF token validation on state-changing operations enables attackers to craft malicious forms or links that trigger unauthorized data modifications.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations and validate Origin/Referer headers; additionally sanitize and encode all user-supplied input to prevent stored XSS execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Site Search 360 installation
    Check your web applications, plugins, or integrated services for Site Search 360. Inspect browser developer tools, source code, or installed package lists for 'site-search-360', 'ss360', or related identifiers.
    Affected if Site Search 360 is present in your environment
  2. Determine installed version
    Review package.json, composer.json, plugin metadata, or the Site Search 360 admin dashboard for the exact version number. Compare against any release notes or changelogs from the vendor.
    Affected if The installed version is unknown or falls within the affected range (if published)
  3. Inspect state-changing endpoints for CSRF protection
    Examine the application source code or capture HTTP requests during administrative actions (e.g., saving search configuration, adding synonyms, modifying settings). Verify whether anti-CSRF tokens, Origin header validation, or Referer header checks are present in the request payloads or headers.
    Affected if State-changing operations lack CSRF token validation or header checks
  4. Test for CSRF token absence in forms
    Locate forms that perform state changes (configuration save, user management, content updates). Inspect form HTML or API requests to determine if a CSRF token parameter or custom header is included and validated server-side.
    Affected if Forms or API calls do not include and validate CSRF tokens
  5. Check input sanitization for stored XSS prevention
    Review the code handling user-supplied input in search configurations, custom labels, or content stored by the application. Determine if input is sanitized (e.g., HTML escaping) before storage and encoding applied before output.
    Affected if User input is stored without sanitization, allowing injected scripts to persist

Your environment is affected if Site Search 360 is installed and its state-changing operations lack proper CSRF token validation combined with insufficient input sanitization, enabling stored XSS injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations and validate Origin/Referer headers; additionally sanitize and encode all user-supplied input to prevent stored XSS execution.

Recommended fix Moderate confidence

Update to the latest version of Site Search 360 (check WordPress plugin repository or vendor for version > 2.1.8)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Site Search 360' plugin
  4. 4. Check the current installed version (should be <= 2.1.8)
  5. 5. If an update is available, click 'Update Now' to install the latest version that addresses the CSRF/Stored XSS vulnerability
  6. 6. After updating, verify the new version number in the plugins list
  7. 7. Clear any caching mechanisms if the site uses caching plugins
  8. 8. Test the Site Search 360 functionality to ensure the plugin still works correctly after the update
Caveat Review plugin changelog for any settings or feature changes that may affect your search configuration

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-39530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-39530 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data