dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-6325

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The RomethemeForm For Elementor plugin for WordPress is vulnerable to unauthorized access and modification of data due to a missing capability check on the export_entries, rtformnewform, and rtformupdate functions in all versions up to, and including, 1.1.5. This makes it possible for unauthenticated attackers to export arbitrary form submissions, create new forms, or update any post title or certain metadata.

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 confidence

The RomethemeForm For Elementor WordPress plugin versions up to 1.1.5 lacks capability checks on three AJAX functions (export_entries, rtformnewform, rtformupdate), allowing unauthenticated attackers to export sensitive form submissions, create arbitrary forms, and modify post titles/metadata without any authentication or authorization.

MitigationUpdate the plugin to version 1.1.6 or later where capability checks have been added; if no patch is available, disable the plugin or restrict AJAX endpoints at the web server level until a fix is released.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'RomethemeForm For Elementor' in the list. Alternatively, check the /wp-content/plugins/romethemeform-for-elementor directory exists on the server.
    Affected if The RomethemeForm For Elementor plugin is present on the WordPress site
  2. Identify installed version
    In the plugins list, check the version number displayed under the plugin name. Or open the main plugin file (usually romethemeform-for-elementor.php) and look for the 'Version:' header comment.
    Affected if The installed version is 1.1.5 or any earlier version (the vulnerability affects versions up to 1.1.5)
  3. Test AJAX endpoint accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=rtformnewform or action=rtformupdate or action=export_entries, without providing any authentication cookies or nonce tokens. Use a tool like curl: curl -X POST https://your-site.com/wp-admin/admin-ajax.php -d 'action=rtformnewform'
    Affected if The AJAX endpoint returns a successful response (HTTP 200) without requiring authentication, indicating the capability check is missing

A user is affected if the RomethemeForm For Elementor plugin version 1.1.5 or earlier is installed AND the AJAX endpoints respond without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.1.6 or later where capability checks have been added; if no patch is available, disable the plugin or restrict AJAX endpoints at the web server level until a fix is released.

Recommended fix Moderate confidence

Update to version 1.2.0 or later (check WordPress plugin repository for latest release)

  1. Check the current version of the RomethemeForm For Elementor plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate RomethemeForm For Elementor and note the current version number
  4. If the installed version is 1.1.5 or earlier, navigate to Plugins > Add New > Upload Plugin or check for an available update
  5. Update to the latest version available in the WordPress plugin repository (version 1.2.0 or later)
  6. Verify the update was successful and test form functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6325 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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