CVE-2025-6758
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.
NVD · uneditedThe Real Spaces - WordPress Properties Directory Theme theme for WordPress is vulnerable to privilege escalation via the 'imic_agent_register' function in all versions up to, and including, 3.6. This is due to a lack of restriction in the registration role. This makes it possible for unauthenticated attackers to arbitrarily choose their role, including the Administrator role, during user registration.
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.
dbcve analysis · high confidenceThe Real Spaces WordPress theme contains a privilege escalation vulnerability in the imic_agent_register function which fails to restrict the role assigned during user registration. Unauthenticated attackers can register with arbitrary roles including Administrator, granting them full administrative access to the WordPress site.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Real Spaces theme is installedNavigate to Appearance > Themes in WordPress admin dashboard and identify if the Real Spaces theme is activeAffected if Real Spaces theme is the active theme
-
Check installed theme versionView the style.css file of the Real Spaces theme (typically in wp-content/themes/real-spaces/) and locate the Version headerAffected if Version is lower than 3.7 (e.g., 3.6, 3.5, etc.)
-
Verify user registration is enabledGo to Settings > General in WordPress admin and check if 'Anyone can register' is enabledAffected if User registration is enabled site-wide
-
Confirm agent registration endpoint is accessibleTest访问注册页面 (通常为 /agent-register/ 或 similar endpoint used by the theme's imic_agent_register function)Affected if The agent registration form is publicly accessible without authentication
-
Audit for unauthorized administrator accountsNavigate to Users > All Users in WordPress admin and review the list for admin accounts you did not create or that have suspicious usernamesAffected if There are administrator accounts you did not create, especially registered around the time the theme was installed
Your environment is affected if Real Spaces theme version is below 3.7, user registration is enabled, and unauthorized admin accounts exist or the agent registration form is publicly accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the Real Spaces theme to version 3.7 or later which should contain the fix. If an update is unavailable, disable user registration site-wide or implement custom role restrictions on the registration function.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6758 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6758 in production — separate from our analysis above.
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.
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.
- 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