Skip to main content
CVE-2026-93908VulnerabilityPublished Updated

The Real Estate Manager – Property Listing and Agent Management plugin for WordPress is vulnerable to Stored

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-93908· Medium 6.4

Not known to be exploited · CVSS 6.4 Medium.

Data as of 14 Nov 2026, 20:44 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. Weaponized: 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 14 Nov 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 users from untrusted sources and monitor for suspicious activity related to the 'before_price_text' parameter. Avoid granting unnecessary privileges to users and consider disabling or limiting the use of the vulnerable AJAX handler if possible.

Description

The Real Estate Manager plugin for WordPress suffers from a stored cross-site scripting (XSS) vulnerability via the 'before_price_text' parameter in all versions up to and including 7.3. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view the affected pages. This vulnerability arises due to insufficient input sanitization and output escaping, lack of capability, nonce, or ownership checks on the AJAX handler, and the use of update_post_meta which bypasses typical filtering mechanisms.

References

Community reviews

Loading reviews…