CVE-2023-44025
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 · uneditedSQL injection vulnerability in addify Addifyfreegifts v.1.0.2 and before allows a remote attacker to execute arbitrary code via a crafted script to the getrulebyid function in the AddifyfreegiftsModel.php component.
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 confidenceSQL injection vulnerability in the getrulebyid function of AddifyfreegiftsModel.php in the Addifyfreegifts WordPress/WooCommerce plugin versions 1.0.2 and earlier allows unauthenticated remote attackers to inject malicious SQL queries, potentially leading to arbitrary code execution or complete database compromise.
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< 1.2.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Addify Free Gifts plugin is installedLog into WordPress admin, go to Plugins > Installed Plugins, and look for 'Addify Free Gifts' in the list of active or inactive pluginsAffected if The plugin appears in the installed plugins list regardless of activation status
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Addify Free Gifts, and note the version number displayed below the plugin nameAffected if The version listed is 1.0.2 or any version below 1.2.0
-
Confirm the vulnerable file existsAccess the WordPress site via file manager or FTP, navigate to /wp-content/plugins/addify-free-gifts/includes/Model/ and verify AddifyfreegiftsModel.php existsAffected if The file AddifyfreegiftsModel.php exists in the expected path and contains a function named getrulebyid
-
Check if the plugin is processing user inputReview web server access logs for requests to the site that include parameters which may be processed by the plugin (common endpoints are /?addify_route=getrulebyid or similar AJAX endpoints)Affected if The plugin is active and handling requests that pass parameters to the getrulebyid function
Your environment is affected if Addify Free Gifts plugin version 1.0.2 or below is installed and active, with the vulnerable getrulebyid function exposed to unauthenticated requests.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.2.0
Upgrade to a patched version of Addifyfreegifts immediately. If no patch is available, disable the plugin until a fix can be implemented. Alternatively, implement input validation and use parameterized queries in the getrulebyid function.
Upgrade Addifyfreegifts module to version 1.2.0 or later
- Backup your PrestaShop database and files before proceeding
- Navigate to the PrestaShop back office > Modules > Module Manager
- Locate the 'Free Gifts' (Addifyfreegifts) module
- Uninstall the current vulnerable version of the module
- Download the patched version 1.2.0 or later from the official addify source or PrestaShop Addons marketplace
- Upload and install the new version of the Free Gifts module
- Configure the module settings as needed
- Test the module functionality to ensure it works correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44025 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-44025 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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