dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-30085

CRITICAL · 9.2 CVSS v4.0 Published 2025-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Remote code execution vulnerability in RSForm!pro component 3.0.0 - 3.3.14 for Joomla was discovered. The issue occurs within the submission export feature and requires administrative access to the export feature.

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

A remote code execution vulnerability exists in the RSForm!Pro Joomla component (versions 3.0.0-3.3.14) within the submission export feature. An attacker with administrative access to the export functionality can execute arbitrary code on the server due to insufficient input validation or insecure handling of export parameters.

MitigationUpdate RSForm!Pro to the latest version beyond 3.3.14 when available. Until patched, restrict administrative access to trusted users only and consider disabling the export feature if not required.

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
High
Authentication
None
User interaction
None
Scope
N

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:X/V:X/RE:L/U:Clear

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. Identify if RSForm!Pro component is installed
    Check for the presence of the RSForm!Pro component in the Joomla administrator components directory or via the Joomla extensions manager
    Affected if RSForm!Pro is present in the Joomla installation
  2. Determine installed RSForm!Pro version
    Locate the version information for RSForm!Pro - typically found in the component manifest file, version.php file within the component directory, or the Joomla extensions database table
    Affected if The installed version falls within 3.0.0 through 3.3.14 inclusive
  3. Verify export functionality is accessible
    Confirm the submission export feature is enabled and accessible within the RSForm!Pro administrative interface under the Forms Manager or Submissions area
    Affected if The export feature is enabled and accessible to administrative users
  4. Confirm administrative access scope
    Review user accounts with access to the RSForm!Pro export functionality in Joomla's user access level settings
    Affected if Multiple untrusted or compromised accounts have administrative access to the export feature

The environment is affected if RSForm!Pro version 3.0.0 through 3.3.14 is installed with the export feature enabled and accessible to users who could be targeted or compromised.

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 RSForm!Pro to the latest version beyond 3.3.14 when available. Until patched, restrict administrative access to trusted users only and consider disabling the export feature if not required.

Recommended fix Moderate confidence

Latest RSForm!Pro version available at rsjoomla.com (beyond version 3.3.14)

  1. 1. Log in to the Joomla administrator panel
  2. 2. Navigate to Components > RSForm!Pro
  3. 3. Backup the current RSForm!Pro installation and database before proceeding
  4. 4. Download the latest version of RSForm!Pro from the official vendor website (rsjoomla.com)
  5. 5. Install the updated RSForm!Pro package through Joomla's extension manager
  6. 6. Verify the installation by checking the component version in Components > RSForm!Pro > Configuration
  7. 7. Test the submission export feature to confirm functionality works as expected
  8. 8. Review user access permissions for the export feature to ensure only necessary administrators have access
Caveat Review release notes for any configuration or feature changes between your current version and the latest version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30085 — 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-2025-30085 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