dbcve.org
Rest Api To MiniprogramWordPress extension · Jianbo

CVE-2024-8484

HIGH · 7.5 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to after 4.7.1 or later.
See remediation →
84/100
Remediation priority · High
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 SQL Injection via the 'order' parameter of the /wp-json/watch-life-net/v1/comment/getcomments REST API endpoint in all versions up to, and including, 4.7.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 versions up to 4.7.1 contain an unauthenticated SQL injection vulnerability in the /wp-json/watch-life-net/v1/comment/getcomments endpoint. The 'order' parameter is not properly escaped before being incorporated into a SQL query, and the existing query lacks prepared statements, allowing attackers to inject arbitrary SQL commands to extract sensitive database information.

MitigationUpdate the plugin to version 4.7.2 or later which contains the security fix. Alternatively, implement proper SQL parameterization/prepared statements for the 'order' parameter in the vulnerable endpoint code.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the installed plugin version
    Locate the plugin in /wp-content/plugins/ (commonly under a folder named 'rest-api-to-miniprogram' or similar), then check the main plugin PHP file or readme.txt for the Version header
    Affected if The installed version is 4.7.1 or lower (any version up to and including 4.7.1)
  2. Verify the vulnerable REST endpoint exists
    Send a GET request to /wp-json/watch-life-net/v1/comment/getcomments (no authentication required) and confirm the endpoint responds with JSON
    Affected if The endpoint is accessible and responds, indicating the plugin is active with the vulnerable code present
  3. Confirm the 'order' parameter is processed by the endpoint
    Send a request to the endpoint with a test 'order' parameter (e.g., ?order=asc) and observe if it influences the SQL query behavior
    Affected if The 'order' parameter is accepted and reflected in the query without proper escaping or prepared statement usage

You are affected if the Jianbo Rest Api To Miniprogram plugin is installed at version 4.7.1 or below AND the /wp-json/watch-life-net/v1/comment/getcomments endpoint is accessible and accepts the 'order' parameter without SQL parameterization.

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 contains the security fix. Alternatively, implement proper SQL parameterization/prepared statements for the 'order' parameter in the vulnerable endpoint code.

Recommended fix Moderate confidence

Upgrade to the latest version available in the WordPress plugin repository (version 4.7.2 or later)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'REST API TO MiniProgram' plugin
  4. Check the current installed version to confirm it is <= 4.7.1
  5. Update the plugin to the latest available version from the WordPress plugin repository

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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