Baidu Tongji GeneratorWordPress extension · Baidu Tongji Generator Project

CVE-2023-31230

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-13
Fix available
A fix is available. Upgrade to after 1.0.2 or later.
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
Cross-Site Request Forgery (CSRF) vulnerability in Haoqisir Baidu Tongji generator allows Stored XSS.This issue affects Baidu Tongji generator: from n/a through 1.0.2.

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 Baidu Tongji generator plugin (versions up to 1.0.2) allows attackers to trick authenticated administrators into submitting malicious requests that result in stored XSS payloads being saved to the application database and executed when viewed by other users.

MitigationImplement anti-CSRF tokens and proper request validation on all state-changing operations; apply output encoding and input validation to prevent stored XSS execution.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Baidu Tongji GeneratorWordPress extension
Affected:<= 1.0.2

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. Identify if Baidu Tongji Generator plugin is installed
    Check your CMS/plugin system for the presence of the Baidu Tongji Generator plugin. Inspect the plugin directory or use system commands to list installed plugins.
    Affected if The plugin is present in the system
  2. Determine the installed version
    Locate the plugin version metadata (typically in a version file, plugin header, or manifest). Compare the version number to the affected range of <= 1.0.2.
    Affected if The installed version is 1.0.2 or lower
  3. Verify admin authentication is possible
    Confirm that administrator-level access exists for the plugin. The CSRF attack requires a logged-in administrator to unknowingly submit the malicious request.
    Affected if Admin accounts with access to the plugin exist in the system
  4. Inspect database for suspicious stored content
    Query application tables where plugin data is stored (e.g., tracking data, configuration storage) for unexpected script tags, HTML, or encoded payloads that could indicate stored XSS.
    Affected if Unusual script tags or HTML fragments are found in plugin-related database records
  5. Review admin action logs for unexpected requests
    Examine server logs, access logs, or application audit trails for admin-initiated requests to plugin endpoints that contain unusual parameters or payload-like data.
    Affected if Admin requests contain suspicious parameter values not generated by normal plugin usage

The environment is affected if the Baidu Tongji Generator plugin version 1.0.2 or lower is installed and active, with admin authentication possible and potential stored XSS payloads present in the database.

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
Upgrade available Upgrade to a release after 1.0.2
Interim mitigation

Implement anti-CSRF tokens and proper request validation on all state-changing operations; apply output encoding and input validation to prevent stored XSS execution.

Fix this in Baidu Tongji Generator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2023-31230 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