dbcve.org
Decoration Management SystemApplication · Code4berry

CVE-2024-11487

HIGH · 8.8 CVSS v3.1 Published 2024-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability has been found in Code4Berry Decoration Management System 1.0 and classified as critical. This vulnerability affects unknown code of the file /decoration/admin/btndates_report.php of the component Between Dates Reports. The manipulation of the argument fromdate/todate leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

SQL injection vulnerability in Code4Berry Decoration Management System 1.0 allows remote attackers to inject malicious SQL code via the fromdate and todate parameters in the /decoration/admin/btndates_report.php file (Between Dates Reports component). The lack of input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries and implement proper input validation for the fromdate and todate parameters. Consider implementing a web application firewall as an additional layer of protection.

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
Decoration Management SystemApplication
Affected:= 1.0

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify the installed Code4Berry Decoration Management System version
    Locate the application installation directory and check for version files, about pages, or metadata that reveal the software version. Common locations include a version.php file, README files, or the admin dashboard.
    Affected if The installed version is Code4Berry Decoration Management System 1.0 exactly.
  2. Verify the presence of the vulnerable component
    Check if the file /decoration/admin/btndates_report.php exists in the web root of the application. Use file system inspection or directory enumeration to confirm its presence.
    Affected if The file btndates_report.php exists in the /decoration/admin/ directory.
  3. Confirm the application exposes the vulnerable parameters
    Review the btndates_report.php source code to confirm it accepts fromdate and todate parameters directly without sanitization or parameterized queries. Check if these parameters are used in SQL statements without proper escaping.
    Affected if The fromdate and todate parameters are processed and used directly in SQL queries without prepared statements or input validation.
  4. Test if the endpoint accepts unauthenticated requests
    Attempt to access /decoration/admin/btndates_report.php directly via HTTP GET or POST request without authentication credentials to determine if the endpoint is publicly accessible.
    Affected if The endpoint is accessible without authentication and accepts the fromdate and todate parameters.

A system is affected if it runs Code4Berry Decoration Management System version 1.0 with the btndates_report.php component accessible and the fromdate/todate parameters processed without parameterized queries.

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

Replace dynamic SQL queries with prepared statements/parameterized queries and implement proper input validation for the fromdate and todate parameters. Consider implementing a web application firewall as an additional layer of protection.

Fix this in Decoration Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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