dbcve.org
Rest Api To MiniprogramWordPress extension · Jianbo

CVE-2024-8485

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to after 4.7.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 REST API TO MiniProgram plugin for WordPress is vulnerable to privilege escalation via account takeovr in all versions up to, and including, 4.7.1 via the updateUserInfo() due to missing validation on the 'openid' user controlled key that determines what user will be updated. This makes it possible for unauthenticated attackers to update arbitrary user's accounts, including their email to a @weixin.com email, which can the be leveraged to reset the password of the user's account, including administrators.

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 REST API TO MiniProgram WordPress plugin has a privilege escalation vulnerability in the updateUserInfo() function. Due to missing server-side validation on the user-controlled 'openid' parameter, unauthenticated attackers can modify arbitrary user accounts, including changing email addresses to @weixin.com. This enables password reset attacks on administrator accounts, leading to full site compromise.

MitigationUpdate the plugin to version 4.7.2 or later which implements proper validation on the 'openid' parameter. If the plugin is unused, remove it entirely.

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
Rest Api To MiniprogramWordPress extension
Affected:<= 4.7.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 if the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Jianbo Rest Api To Miniprogram' or 'REST API TO MiniProgram'. Alternatively, check the /wp-content/plugins/ directory for folders containing 'rest-api-to-miniprogram' or similar naming.
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In WordPress admin, click on the plugin from the Plugins list and view the version number displayed. Alternatively, check the main plugin PHP file header for the Version field, typically found in /wp-content/plugins/rest-api-to-miniprogram/includes/rest-api-to-miniprogram.php or similar main file.
    Affected if The version number is 4.7.1 or lower
  3. Confirm the vulnerable endpoint exists
    Check if the REST API endpoint /wp-json/rest-api-to-miniprogram/v1/userinfo is accessible. This can be tested by making a GET request to that URL without authentication.
    Affected if The endpoint responds and accepts parameters without authentication
  4. Verify if user data can be modified
    Test if the updateUserInfo function accepts and processes the 'openid' parameter by sending a POST request with the 'openid' parameter to the userinfo endpoint, as per the plugin's documented API usage.
    Affected if The API accepts the openid parameter and allows modification of user fields without validation

A user is affected if the Jianbo Rest Api To Miniprogram plugin is installed with version 4.7.1 or lower and the REST API endpoint is accessible without authentication.

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

Update the plugin to version 4.7.2 or later which implements proper validation on the 'openid' parameter. If the plugin is unused, remove it entirely.

Recommended fix High confidence

4.7.2

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the REST API TO MiniProgram plugin
  4. Click 'Update Now' to install the latest version (4.7.2 or later)
  5. After updating, verify the plugin version is 4.7.2 or higher
  6. Audit user accounts for any unauthorized changes, particularly emails changed to @weixin.com
  7. Reset passwords for any administrator accounts that were modified as a precaution
  8. Consider forcing password reset for all users if widespread compromise is suspected

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

Fix this in Rest Api To Miniprogram 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 the upgrade done

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-2024-8485 — 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-2024-8485 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