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

CVE-2025-12456

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The Centangle-Team plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.0. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to modify plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Additionally, due to insufficient input sanitization and output escaping on cai_name_color parameter, this issue allows to inject arbitrary web scripts in pages, that will execute whenever a user accesses an injected page.

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 · high confidence

The Centangle-Team WordPress plugin (versions up to 1.0.0) suffers from a CSRF vulnerability due to missing nonce validation on a settings function, allowing unauthenticated attackers to modify plugin settings via forged requests. Additionally, the cai_name_color parameter lacks input sanitization and output escaping, enabling stored XSS injection that executes when users access affected pages.

MitigationImplement nonce validation on the affected function and apply proper input sanitization (sanitize_text_field/sanitize_hex_color) plus output escaping (esc_attr/esc_html) for the cai_name_color parameter. Consider updating to a patched version once available.

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
None

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

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. Verify Centangle-Team plugin is installed
    Navigate to WordPress Admin > Plugins and check if 'Centangle-Team' appears in the list of installed plugins, or inspect the wp-content/plugins/ directory for a folder named 'centangle-team' or similar.
    Affected if The plugin appears in the installed plugins list.
  2. Check the installed plugin version
    In WordPress Admin > Plugins, click on the plugin to view its details and locate the version number. Alternatively, open the main plugin PHP file (e.g., centangle-team.php) and look for the 'Version' header in the plugin comment block.
    Affected if The installed version is 1.0.0 or any version up to 1.0.0.
  3. Locate the plugin settings page
    In WordPress Admin, look for a 'Team' or 'Centangle Team' menu item under 'Settings' and access any configuration page where team member display settings can be modified.
    Affected if A settings page exists and includes a color or name color configuration option (cai_name_color parameter).
  4. Inspect the cai_name_color parameter handling
    If you have code access, examine the PHP file that handles the plugin settings save action and verify whether the cai_name_color parameter is processed with sanitization functions like sanitize_text_field or sanitize_hex_color, and whether output is escaped with esc_attr or esc_html when displayed.
    Affected if The cai_name_color parameter lacks input sanitization (no sanitize_text_field/sanitize_hex_color) and output escaping (no esc_attr/esc_html) in the code.
  5. Verify nonce validation on settings save
    Examine the PHP function that processes the settings form submission and check if a nonce field is verified using wp_verify_nonce or check_admin_referer before processing the request.
    Affected if No nonce verification is performed before processing settings changes.

A user is affected if the Centangle-Team plugin (version 1.0.0 or earlier) is installed, the plugin settings page with the cai_name_color parameter is accessible, and the code lacks proper nonce validation and input sanitization/escaping for that parameter.

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 nonce validation on the affected function and apply proper input sanitization (sanitize_text_field/sanitize_hex_color) plus output escaping (esc_attr/esc_html) for the cai_name_color parameter. Consider updating to a patched version once available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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