← Back to results
Vulnerability record · public intelligence
CVE-2012-10010
MEDIUM

BestWebSoft Contact Form contact_form.php cntctfrm_settings_page cross-site request forgery

Published Apr 9, 2023 · Updated Nov 3, 2026

Severity · CVSSMEDIUM · Not scored
Known exploitationNot listed
EPSS / likelihood0.36%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

BestWebSoft Contact Form contact_form.php cntctfrm_settings_page cross-site request forgery

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

A vulnerability was found in BestWebSoft Contact Form 3.21. It has been classified as problematic. This affects the function cntctfrm_settings_page of the file contact_form.php. The manipulation leads to cross-site request forgery. It is possible to initiate the attack remotely. Upgrading to version 3.22 is able to address this issue. The identifier of the patch is 8398d96ff0fe45ec9267d7259961c2ef89ed8005. It is recommended to upgrade the affected component. The identifier VDB-225321 was assigned to this vulnerability.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. vuldb.com ↗
  2. vuldb.com ↗
  3. Patch commit ↗

Record history

Published Apr 9, 2023 · Last refreshed Nov 3, 2026