Quick answers
- Is CVE-2026-78083 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78083 being exploited in the wild.
- How severe is CVE-2026-78083?
- Informational severity, published 10 September 2026.
- Which products and versions are affected?
- JoomShaper SP Property < 4.1.4.
- Is there a fix for CVE-2026-78083?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-78083 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-78083?
- Check whether you run JoomShaper SP Property at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A CSRF (Cross-Site Request Forgery) vulnerability exists in the SP Property component's properties.booking and agents.sendmail endpoints. These endpoints process POST requests without validating Joomla's anti-CSRF session tokens, allowing an attacker to craft a malicious page that, when visited by an authenticated user, silently submits forged booking or contact requests. The vulnerability requires a victim to visit an attacker-controlled page while logged into a Joomla site with SP Property installed, but involves no complex interaction or social engineering beyond the visit itself. An attacker can abuse this to spam property bookings, submit false agent contact requests, or generate fraudulent leads, disrupting business operations and data integrity. The issue affects SP Property versions prior to 4.1.4.
Affected products
- JoomShaper SP Property < 4.1.4
Timeline
- 2026-09-10: disclosed