dbcve.org
App BuilderWordPress extension · Appcheap

CVE-2024-31282

MEDIUM · 6.1 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 3.8.8 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
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in Appcheap.Io App Builder.This issue affects App Builder: from n/a through 3.8.7.

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

Open redirect vulnerability in Appcheap.Io App Builder allows attackers to craft malicious URLs that redirect users to untrusted sites. The application likely accepts a redirect parameter without proper validation of the target URL, enabling phishing and credential theft attacks.

MitigationImplement strict URL validation to ensure all redirect targets point to trusted, whitelisted domains before performing any redirection.

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
App BuilderWordPress extension
Affected:< 3.8.8

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 Appcheap App Builder is deployed
    Check your application documentation, installed packages, or system inventory to confirm the application is Appcheap Io App Builder. Look for references to 'Appcheap' or 'App Builder' in your software manifest or dependencies.
    Affected if The software is confirmed to be Appcheap Io App Builder
  2. Determine the installed version
    Locate the version information for your Appcheap App Builder installation. Check the package.json file, composer.json, or the application's about/versions page if available. Compare your version against 3.8.8.
    Affected if The installed version is below 3.8.8 (e.g., 3.8.7, 3.8.0, any version < 3.8.8)
  3. Identify redirect parameter usage
    Search your application configuration and code for parameters that handle URL redirection. Look for common redirect parameter names such as 'redirect', 'return_url', 'url', 'next', or 'target' in query strings, form submissions, or API endpoints.
    Affected if The application accepts a redirect parameter in URLs or form inputs without documented whitelist validation
  4. Test redirect parameter behavior
    Submit a request to your application with a redirect parameter pointing to an external domain, such as redirect=https://example.com. Observe if the application performs an unrestricted redirect to the provided URL.
    Affected if The application redirects to the arbitrary URL provided in the redirect parameter without validating it against a whitelist of trusted domains

You are affected if your environment runs Appcheap App Builder version below 3.8.8 and the application processes unvalidated redirect parameters.

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 3.8.8 or later
Fixed in 3.8.8
Interim mitigation

Implement strict URL validation to ensure all redirect targets point to trusted, whitelisted domains before performing any redirection.

Recommended fix Moderate confidence

3.8.8

  1. 1. Back up your current App Builder installation and database before proceeding with any updates.
  2. 2. Update App Builder to version 3.8.8 or later.
  3. 3. After upgrading, verify that the open redirect vulnerability is resolved by testing with untrusted URL inputs.
  4. 4. Confirm all application functionality remains working as expected after the upgrade.

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

Fix this in App Builder 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 the upgrade done

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