Skip to main content
VulnerabilityPublished Updated

CVE-2026-93908: Real Estate Manager (WordPress plugin) · Cross-site Scripting

Affects Real Estate Manager (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 6.4 Medium.

Data as of 26 Oct 2026, 17:30 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
rameez_iqbalReal Estate Manager – Property Listing and Agent ManagementAffected
  • <=7.3
Fixed in–

AI-suggested

Until a fix is available, restrict subscriber-level user capabilities where possible and monitor for suspicious activity related to the 'before_price_text' parameter. Applying strict input validation and output escaping on this parameter in custom code or through security plugins may reduce risk.

Description

The Real Estate Manager – Property Listing and Agent Management WordPress plugin up to version 7.3 is vulnerable to stored cross-site scripting (XSS) via the 'before_price_text' parameter. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view the affected pages. The vulnerability arises from insufficient input sanitization and lack of capability, nonce, or ownership checks in the AJAX handler responsible for saving this data. Because the injected value is stored in post metadata rather than post content, standard WordPress filtering does not apply.

References

Community reviews

Loading reviews…