CVE-2024-13307
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 Reales WP - Real Estate WordPress Theme theme for WordPress is vulnerable to unauthorized modification and loss of data due to a missing capability check on the 'reales_delete_file', 'reales_delete_file_plans', 'reales_add_to_favourites', and 'reales_remove_from_favourites' functions in all versions up to, and including, 2.1.2. This makes it possible for unauthenticated attackers to delete arbitrary attachments, and add or remove favorite property listings for any user.
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 Reales WP theme versions up to 2.1.2 contains multiple AJAX functions (reales_delete_file, reales_delete_file_plans, reales_add_to_favourites, reales_remove_from_favourites) that lack proper capability checks, enabling unauthenticated attackers to delete arbitrary file attachments and modify favorite property listings for any user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- 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.
-
Confirm Reales WP theme is installedCheck the WordPress themes directory for the 'reales-wp' or 'Reales' theme folder, or view the theme in WordPress admin under Appearance > ThemesAffected if The theme folder exists in wp-content/themes/
-
Identify installed theme versionOpen the theme's style.css file (usually in wp-content/themes/reales-wp/style.css) and look for the 'Version:' header in the file commentsAffected if The version listed is 2.1.2 or lower
-
Verify AJAX endpoint accessibilityCheck the theme's functions.php or ajax.php for the action hooks: 'wp_ajax_reales_delete_file', 'wp_ajax_nopriv_reales_delete_file', 'wp_ajax_reales_delete_file_plans', 'wp_ajax_nopriv_reales_delete_file_plans', 'wp_ajax_reales_add_to_favourites', 'wp_ajax_nopriv_reales_add_to_favourites', 'wp_ajax_reales_remove_from_favourites', 'wp_ajax_nopriv_reales_remove_from_favourites'Affected if The 'nopriv' hooks exist for any of these actions (indicating unauthenticated access is allowed)
-
Inspect capability check implementationExamine the PHP functions handling these AJAX calls (reales_delete_file, reales_delete_file_plans, reales_add_to_favourites, reales_remove_from_favourites) to see if they call current_user_can() or similar authorization checks before performing actionsAffected if No capability checks (current_user_can, check_admin_referer, nonce verification) are found in these functions
A user is affected if they have Reales WP theme version 2.1.2 or earlier installed AND the AJAX endpoints are exposed without capability checks, allowing unauthenticated file deletion or favorite modification.
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.
From vendor dataUpdate the theme to version 2.1.3 or later which implements proper capability checks; alternatively, disable these AJAX endpoints or add custom access controls at the server level if the update is unavailable.
- 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-13307 — 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-13307 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