CVE-2026-57641: Unauthenticated CSRF in Real Estate 7 ≤3.5.9
Real Estate 7 versions 3.5.9 and earlier are vulnerable to cross-site request forgery (CSRF) attacks that do not require prior authentication. An attacker can trick a user into unknowingly triggering malicious actions within the application by hosting a specially crafted webpage or email. Since the vulnerability allows unauthenticated exploitation, any visitor to a compromised site or user who clicks a malicious link is at risk, regardless of whether they have an active session in Real Estate 7.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- CWE-352
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-26 / 2026-06-26
NVD description (verbatim)
Unauthenticated Cross Site Request Forgery (CSRF) in Real Estate 7 <= 3.5.9 versions.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-57641 is an unauthenticated CSRF vulnerability (CWE-352) in Real Estate 7 up to version 3.5.9. The application fails to implement or properly validate anti-CSRF tokens on state-changing requests, allowing attackers to craft requests that execute on behalf of users without their knowledge or consent. The vulnerability has a CVSS 3.1 score of 6.5 (MEDIUM), with a vector indicating network-based attack (AV:N), low complexity (AC:L), no privileges required (PR:N), and user interaction required (UI:R). Impact is limited to availability (A:H), suggesting the attack primarily disrupts service rather than compromising confidentiality or integrity.
Business impact
CSRF exploitation can lead to unintended data modifications, service disruptions, or unauthorized transactions within Real Estate 7 installations. Depending on the application's functionality, attackers could alter property listings, manipulate transaction states, or trigger administrative actions. While the CVSS rating reflects availability as the primary impact, the reputational and operational consequences of unexplained changes to user accounts or listings can erode customer trust. Organizations must assume that any user with a Real Estate 7 session is vulnerable if they visit an attacker-controlled site.
Affected systems
Real Estate 7 versions 3.5.9 and earlier are affected. The vulnerability is unauthenticated, meaning any deployment of these versions is potentially exploitable regardless of network exposure or user role. Verify your deployed version immediately; if you are running version 3.5.9 or below, your installation requires remediation.
Exploitability
This vulnerability requires user interaction (a user must visit a malicious site or click a link) but no authentication, making it a practical attack vector. An attacker needs only basic knowledge of HTML and web requests to craft an exploit. Public disclosure date has passed (published June 26, 2026), and the lack of KEV listing does not indicate maturity of exploitation—CSRF vulnerabilities are trivial to weaponize once the flaw is known. Assume active exploitation is possible.
Remediation
Upgrade Real Estate 7 to a version higher than 3.5.9. Verify the exact patched version number against the vendor's official advisory and changelog. Until patching is possible, implement network-level mitigations such as restricting access to Real Estate 7 administrative interfaces, enforcing HTTPS with secure cookie flags (SameSite attribute), and educating users to avoid clicking links from untrusted sources while logged into the application.
Patch guidance
Contact your Real Estate 7 vendor or check their official advisory for the release containing the fix. Verify against the vendor's security bulletin to confirm the version resolves CVE-2026-57641 before deploying. Test the update in a non-production environment first. Apply the patch as soon as feasible, prioritizing instances exposed to untrusted networks or handling sensitive transactions.
Detection guidance
Monitor for unexpected state-changing requests (POST, PUT, DELETE) originating from external referrers or lacking proper CSRF token validation. Log and inspect admin actions that lack typical user session context. Review web server and application logs for requests with suspicious Referer headers or missing Referer/Origin fields on sensitive operations. Implement or review your CSRF token validation logic to ensure tokens are session-bound and verified on all state-altering endpoints.
Why prioritize this
Although rated MEDIUM severity, this vulnerability is unauthenticated and requires only user interaction, lowering the barrier to exploitation. Any user session in a vulnerable Real Estate 7 instance can be hijacked to perform unintended actions. The lack of authentication requirement and the ease of CSRF exploitation warrant treating this as a higher operational priority than the CVSS score alone suggests. Patch this within your normal critical/high queue.
Risk score, explained
CVSS 3.1 score of 6.5 reflects the attack complexity (network, low complexity), lack of privilege requirement, and mandatory user interaction. The 'High' availability impact (A:H) suggests significant service disruption potential, though integrity and confidentiality are not directly compromised. The score appropriately captures that exploitation is practical and widespread impact is possible, but the need for user interaction prevents a higher rating. Context matters: if Real Estate 7 handles financial transactions, upgrade the priority above the CVSS score.
Frequently asked questions
Can an attacker exploit this vulnerability without the user visiting a malicious site?
No. CVSS notation UI:R (user interaction required) means the user must visit a malicious webpage, click a crafted link, or perform another interactive step. However, this is a low bar—attackers can embed payloads in emails, ads, or seemingly legitimate resources.
If a user is not logged into Real Estate 7, are they still at risk?
No, the CSRF attack requires an active session. However, many users remain logged into web applications across browser sessions, making this a realistic threat. Best practice is to assume some user population is always logged in.
Does this vulnerability allow attackers to steal passwords or access real estate data directly?
No. CSRF cannot be used to read data or steal credentials. The vulnerability allows attackers to perform actions on behalf of a logged-in user—such as modifying listings or state—but cannot exfiltrate sensitive information.
What versions of Real Estate 7 are safe?
Any version higher than 3.5.9 is presumed safe, pending official vendor confirmation. Verify the exact patched version in the vendor's security advisory before assuming a version is secure.
This analysis is provided for informational purposes and does not constitute legal, compliance, or professional security advice. Patch version numbers and timelines must be verified directly with your vendor's official security advisory. SEC.co makes no warranty regarding the completeness or accuracy of this intelligence. Organizations are responsible for validating patch applicability and testing in their environments. Exploitation status, active attacks, and vendor patch releases may change after publication; refer to official sources for current information. Source: NVD (public-domain), retrieved 2026-08-05. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20067MEDIUMWordPress CP Polls CSRF Vulnerability
- CVE-2016-20074MEDIUMWordPress Lazy Content Slider CSRF Vulnerability – Patch & Detection Guide
- CVE-2016-20083MEDIUMWordPress More Fields Plugin CSRF Vulnerability – Exploitation, Remediation & Detection
- CVE-2018-25387MEDIUMHaPe PKH 1.1 Cross-Site Request Forgery (CSRF) Admin Password Reset
- CVE-2018-25397MEDIUMCSRF Vulnerability in PHP-SHOP 1.0 – Admin Account Injection
- CVE-2018-25435MEDIUMZeusCart 4.0 CSRF Vulnerability – Account Deactivation Risk
- CVE-2022-44630MEDIUMYITH WooCommerce Product Slider Carousel CSRF Vulnerability
- CVE-2022-47150MEDIUMCSRF Vulnerability in WooCommerce Conversion Tracking Plugin – Patch Guidance