Arforms Form BuilderWordPress extension · Reputeinfosystems
CVE-2024-37920
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Repute InfoSystems ARForms Form Builder allows Reflected XSS.This issue affects ARForms Form Builder: from n/a through 1.6.7.
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 · moderate confidenceReflected XSS vulnerability in ARForms Form Builder allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in the web page. The CVSS 6.1 score indicates the vulnerability is exploitable but may require user interaction.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Arforms Form BuilderWordPress extension
< 1.6.8CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify ARForms Form Builder installationLocate the ARForms plugin/theme files in your WordPress installation. Check the main plugin file or version file for the installed version number.Affected if The installed version is found to be less than 1.6.8 (e.g., 1.6.7, 1.6.6, earlier versions).
-
Verify plugin version via WordPress adminNavigate to WordPress dashboard > Plugins > ARForms Form Builder and check the version displayed, or query the database plugin version record if accessible.Affected if The reported version is any version below 1.6.8.
-
Confirm plugin is active and in useCheck if ARForms Form Builder is activated and has active forms on the site. Review the wp_options table or plugin admin interface for enabled forms.Affected if The plugin is active and forms are published, exposing the vulnerable code to site visitors.
You are affected if ARForms Form Builder is installed and the installed version is below 1.6.8, with the plugin active and handling user-submitted form data.
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.
dbcve · scoped1.6.8
Update ARForms Form Builder to the latest patched version. If no update is available, implement output encoding and input validation on all form parameters, particularly those handling user-submitted data.
ARForms Form Builder version 1.6.8
- 1. Create a complete backup of your WordPress site including database and files
- 2. Navigate to WordPress admin dashboard > Plugins
- 3. Find ARForms Form Builder in the installed plugins list
- 4. Click 'Update now' if an update is available, or manually upload version 1.6.8
- 5. After updating, verify the plugin version shows 1.6.8 in the plugins list
- 6. Test that forms render correctly and the XSS vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Arforms Form Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37920 — 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-2024-37920 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