Wp RecallWordPress extension · Plechevandrey
CVE-2024-1175
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 · uneditedThe WP-Recall – Registration, Profile, Commerce & More plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'delete_payment' function in all versions up to, and including, 16.26.6. This makes it possible for unauthenticated attackers to delete arbitrary payments.
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 confidenceThe WP-Recall WordPress plugin versions up to 16.26.6 lack a capability check on the delete_payment function, allowing unauthenticated attackers to delete arbitrary payment records from the database. This is an IDOR vulnerability combined with missing authorization on an administrative function.
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
Wp RecallWordPress extension
< 16.26.6CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if WP-Recall plugin is installedInspect the WordPress plugins directory at wp-content/plugins/ for a folder named wp-recall, or use WP-CLI: wp plugin list --name='wp-recall'Affected if The WP-Recall plugin folder exists in the plugins directory
-
Determine installed WP-Recall versionRead the version header from the main plugin file (commonly wp-content/plugins/wp-recall/wp-recall.php), or run: wp plugin get wp-recall --field=versionAffected if The version returned is lower than 16.26.6
-
Verify plugin activation statusRun: wp plugin is-active wp-recall, or check via WordPress admin under Plugins > Installed PluginsAffected if The plugin is currently active and the version is below 16.26.6
-
Confirm the delete_payment function is presentSearch the plugin files for the delete_payment function definition, typically in core class files under wp-content/plugins/wp-recall/core/Affected if The function exists in the installed version and the version is below 16.26.6
The environment is affected if WP-Recall plugin version is below 16.26.6 and the plugin is active, as the vulnerable delete_payment function lacks capability checks.
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 · scoped16.26.6
Update the WP-Recall plugin to version 16.26.7 or later which includes proper capability checks on the delete_payment function. Until then, consider disabling the affected functionality or restricting access at the server level.
Version 16.26.7 or later (latest available version)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the WP-Recall plugin in the list
- 4. If an update is available, click 'Update Now' to upgrade to the latest version (16.26.7 or higher)
- 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
- 6. Verify the update completed successfully by checking the plugin version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Recall
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-1175 — 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-2024-1175 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