dbcve.org
Testimonial Page ManagerApplication · Remyandrade

CVE-2024-1196

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

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
A vulnerability classified as problematic was found in SourceCodester Testimonial Page Manager 1.0. This vulnerability affects unknown code of the file add-testimonial.php of the component HTTP POST Request Handler. The manipulation of the argument name/description/testimony leads to cross site scripting. The attack can be initiated remotely. VDB-252694 is the identifier assigned to this vulnerability.

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 confidence

Stored XSS vulnerability in SourceCodester Testimonial Page Manager 1.0 where the add-testimonial.php script accepts unsanitized user input through the name, description, and testimony POST parameters, allowing injection of malicious JavaScript that executes when testimonials are displayed to other users.

MitigationImplement input validation and output encoding: sanitize all user-supplied input using htmlspecialchars() or equivalent functions before storage, and apply contextual encoding when rendering testimonial content to prevent script execution.

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
Testimonial Page ManagerApplication
Affected:= 1.0

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
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 checks

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

  1. Confirm Testimonial Page Manager 1.0 is installed
    Locate and identify the SourceCodester Testimonial Page Manager application on the system, typically in the web server document root. Check for the presence of PHP files associated with this application.
    Affected if The application is SourceCodester Testimonial Page Manager version 1.0
  2. Verify add-testimonial.php exists
    Locate the add-testimonial.php file within the application directory structure. This is the vulnerable script that accepts the name, description, and testimony POST parameters.
    Affected if The add-testimonial.php script is present and accessible via the web server
  3. Check if testimonials are stored and displayed
    Identify if there is functionality to display stored testimonials to users. Look for scripts or pages that retrieve and render testimonial data from storage (such as a database or file).
    Affected if Testimonial data is being retrieved and rendered on pages accessible to users
  4. Inspect input handling in add-testimonial.php
    Review the source code of add-testimonial.php to determine if the name, description, and testimony POST parameters are sanitized before storage. Look for absence of htmlspecialchars() or equivalent encoding functions.
    Affected if The POST parameters name, description, and testimony are stored without sanitization (no htmlspecialchars() or similar functions used)
  5. Inspect output handling when displaying testimonials
    Review the source code of pages that display testimonials to determine if output encoding is applied when rendering the stored name, description, and testimony values. Look for absence of contextual encoding.
    Affected if Stored testimonial content is rendered to users without output encoding

If Testimonial Page Manager 1.0 is installed with add-testimonial.php present, and testimonials can be stored and displayed without input sanitization or output encoding, the environment is affected by CVE-2024-1196.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and output encoding: sanitize all user-supplied input using htmlspecialchars() or equivalent functions before storage, and apply contextual encoding when rendering testimonial content to prevent script execution.

Fix this in Testimonial Page Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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