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

CVE-2025-23869

HIGH · 7.1 CVSS v3.1 Published 2025-01-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 shibulijack CJ Custom Content cj-custom-content allows Stored XSS.This issue affects CJ Custom Content: from n/a through <= 2.0.

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

A CSRF vulnerability in the CJ Custom Content plugin (versions <= 2.0) allows attackers to inject malicious JavaScript through stored XSS. By tricking an authenticated administrator into triggering a forged request, attackers can persistently embed scripts that execute in the browsers of other users viewing the affected content.

MitigationImplement WordPress nonces (CSRF tokens) for all admin actions that modify content, and ensure all user-supplied data is properly sanitized before storage and escaped during output.

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. Check CJ Custom Content plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'CJ Custom Content' in the list; the version number is displayed below the plugin name. Alternatively, inspect the main plugin file (commonly /wp-content/plugins/cj-custom-content/cj-custom-content.php) and look for the 'Version:' header in the plugin comment block.
    Affected if the displayed version is 2.0 or below, or if the version field cannot be found (indicating an old/unmaintained release)
  2. Confirm plugin is active
    Verify the CJ Custom Content plugin is currently activated in the WordPress site. In admin, check Plugins > Installed Plugins - the plugin should have an 'Active' label or be highlighted as enabled.
    Affected if the plugin is currently active on the WordPress installation
  3. Inspect admin action nonces
    Examine the PHP source files of the plugin, particularly any files handling admin form submissions (look for files in an /admin/ subfolder or containing form handlers). Search for missing calls to wp_verify_nonce() or check_admin_referer() before processing admin POST/GET requests that save or modify content.
    Affected if admin actions that modify content lack CSRF token verification (the code does not call nonce verification functions)
  4. Check for stored content lack of sanitization
    In the plugin PHP files, locate where user-supplied data is saved to the database (typically insert/update operations) and where it is output to users. Verify if functions like sanitize_text_field(), esc_attr(), or esc_html() are used on input and output respectively.
    Affected if user-supplied data stored or displayed by the plugin is not sanitized/escaped using WordPress sanitization functions
  5. Review stored content for injected scripts
    In WordPress database, query the posts or custom tables used by the plugin for any stored JavaScript, script tags, or iframe elements that were not intentionally added. Access wp-admin > all content types managed by the plugin and inspect page source for unexpected script tags.
    Affected if the database contains suspicious script tags or malicious payloads in content created via this plugin

If the CJ Custom Content plugin version is 2.0 or below, is active, and admin actions lack CSRF token verification, the environment is vulnerable to CVE-2025-23869; additionally inspect stored content for any injected malicious scripts.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces (CSRF tokens) for all admin actions that modify content, and ensure all user-supplied data is properly sanitized before storage and escaped during output.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23869 — 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-23869 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