Unrestricted File UploadWeakness · CWE-434

CVE-2025-2891

HIGH · 8.8 CVSS v3.1 Published 2025-04-01

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

NVD · unedited

The Real Estate 7 WordPress theme for WordPress is vulnerable to arbitrary file uploads due to missing file type validation via the 'template-submit-listing.php' file in all versions up to, and including, 3.5.4. This makes it possible for authenticated attackers, with Seller-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible if front-end listing submission has been enabled.

Technical summary

dbcve analysis · high confidence

The Real Estate 7 WordPress theme lacks file type validation in template-submit-listing.php, allowing authenticated users with Seller-level access to upload arbitrary files when front-end listing submission is enabled. This can lead to remote code execution if executable files like PHP are uploaded.

MitigationDisable front-end listing submission until a patched version (3.5.5+) is available, or add server-side file type validation restricting uploads to permitted file extensions only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Real Estate 7 theme version

Check the theme version in WordPress dashboard under Appearance > Themes, or inspect style.css in the theme directory for the Version: header

Affected if Installed version is below 3.5.5 (the patch was released in version 3.5.5+)
Verify front-end listing submission is enabled

In WordPress admin, navigate to the Real Estate 7 theme settings and check if the 'Submit Listing' or front-end listing submission feature is turned on

Affected if Front-end listing submission is enabled and the theme is vulnerable (<3.5.5)
Confirm template-submit-listing.php exists

Locate the file template-submit-listing.php in the theme directory (typically /wp-content/themes/realestate-7/) and verify it is present

Affected if The file exists and the theme version is vulnerable (<3.5.5)
Check for Seller-level user accounts

In WordPress admin, go to Users and review roles; Seller is a custom role in this theme that can submit listings

Affected if Users with Seller role exist and the vulnerable submission feature is enabled

You are affected if the Real Estate 7 theme version is below 3.5.5 AND front-end listing submission is enabled, allowing authenticated Seller-level users to potentially upload arbitrary executable files.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Disable front-end listing submission until a patched version (3.5.5+) is available, or add server-side file type validation restricting uploads to permitted file extensions only.

Recommended fix Moderate confidence

Real Estate 7 theme version 3.5.5 or latest available version

Check the current version of the Real Estate 7 theme installed on your WordPress site
Upgrade to version 3.5.5 or later of the Real Estate 7 theme (the description indicates versions up to 3.5.4 are affected)
If upgrade is not immediately possible, disable front-end listing submission in theme settings to reduce attack surface
Verify the upgrade was successful and the vulnerability is resolved
Ensure users with Seller-level access are limited to trusted individuals only

Caveat Standard theme update; test any custom templates or child theme modifications after upgrading

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

Have this fixed Scoped from the published advisory

Consultation1.0 h
Implementation3.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,220

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2891 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-2891?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 0.7%

Remediation

A high-priority fix

Have this fixed 7 hrs · Moderate

Typical engagement from $1,220

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-2891 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References